fix(android): Leaking listeners

[mateuuszzzzz]

This PR fixes three leaks of listeners:

1. Extracted listener that waits for CONTENT_APPEARED and RELOAD to a constant to prevent leak when module is invalidated. Now we remove this listener in invalidate.
2. RNPerformance.removeListener had an incorrect condition that prevented listeners from being removed.
3. Extracted another listener that is added on startup to prevent multiple identical listeners from being added. Since getPackages can be called multiple times in React Native, the PerformancePackage constructor may also be invoked multiple times, resulting in several identical listeners being added as different instances. ReactMarker prevents duplicates only when the same instance is added, so extracting the listener to a static constant resolves this issue.

Additionally I changed onCatalystInstanceDestroyed to invalidate, because previous method is deprecated.

[war-in]

I don't think we need a separate method for it :)

[mateuuszzzzz]

Right, I wanted to make this look similar to setupNativeMarkerListener which was already in the codebase

[war-in]

Shouldn't we remove the other listener too?

[mateuuszzzzz]

startupMarkerListener is specific, because once we add it to ReactMarker (singleton) it can stay there through the whole app lifetime.

I.e.:

1. We add it once (by storing it in a static constant, ReactMarker will know that this listener has already been added, so it won’t add it again, preventing duplication when PerformancePackage constructor is called multiple times).
2. We don’t need to remove it in invalidate because this listener isn’t bound to the native module’s lifetime.

[mateuuszzzzz]

Hi @oblador! Would you have some time to review this PR? 🙏

[oblador]

I had been avoiding migrating to invalidate to keep bw compatibility, but since it's been there since 0.74 I think it should be fine to drop it now.