fix(android): fragment memory leak in RNSentryReactFragmentLifecycleTracer

[minhuwv]

📢 Type of change

• Bugfix
• New feature
• Enhancement
• Refactoring

📜 Description

Resolve fragment memory leak by removing EventDispatcherListener added in onFragmentViewCreated after onFragmentViewDestroyed is called.

💡 Motivation and Context

Originally, we only remove EventDispatcherListener when received ScreenAppearEvent
this behavior cause Fragment memory leak.

If the Fragment is destroyed before the ScreenAppearEvent arrives, the listener will not be removed from the EventDispatcher. Because of this listener captures v, which is the Fragment's container view,
thereby retaining a reference to the Fragment and ultimately causing a memory leak.

💚 How did you test it?

📝 Checklist

• I added tests to verify changes.
• No new PII added or SDK only sends newly added PII if sendDefaultPII is enabled.
• I updated the docs if needed.
• I updated the wizard if needed.
• All tests passing.
• Public API changes reviewed by another Mobile SDK team member or implemented according to the develop docs spec.
• No breaking changes.

🔮 Next steps

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

Want reviews to match your repository better? Bugbot Learning can learn team-specific rules from PR activity. A team admin can enable Learning in the Cursor dashboard.

^{Reviewed by Cursor Bugbot for commit bc02a80. Configure here.}