Fix ensure ndk libs are loaded before calling close

[markushi]

📜 Description

Ensures the NDK libs are loaded, just like within .init(). The NDK integration itself already swallows any thrown exception, so there should be no change in that regard.

💡 Motivation and Context

💚 How did you test it?

📝 Checklist

• I reviewed the submitted code.
• I added tests to verify the changes.
• No new PII added or SDK only sends newly added PII if sendDefaultPII is enabled.
• I updated the docs if needed.
• Review from the native team if needed.
• No breaking change or entry added to the changelog.
• No breaking change for hybrid SDKs or communicated to hybrid SDKs.

🔮 Next steps

#skip-changelog

[github-actions]

Performance metrics 🚀

	Plain	With Sentry	Diff
Startup time	398.46 ms	420.10 ms	21.64 ms
Size	1.70 MiB	2.35 MiB	667.96 KiB

Previous results on branch: fix/ndk-shutdown

Startup times

Revision	Plain	With Sentry	Diff
0af72d4	444.49 ms	466.86 ms	22.37 ms

App size

Revision	Plain	With Sentry	Diff
0af72d4	1.70 MiB	2.35 MiB	668.12 KiB

[stefanosiano]

this could slow down on SDK restart/double init
i'd rather submit the shutdown() to the same thread we use to load the libraries
wdyt?

[markushi]

I thinks it's fine this way because .init() already waits for the latch to finish, so whenever .close() is called the latch is already counted down. So even a double init wouldn't cause this to be blocking, unless you call SentryAndroid.init() from different threads in parallel 😅
So the .await() will only be blocking in case SentryNdk.close() is called before SentryNdk.init() - in theory this should never happen.