Catch exceptions when closing integrations

[adinauer]

📜 Description

Catch exceptions thrown by Integration.close()

💡 Motivation and Context

An exception thrown by an integration on close interrupts Sentry.close() which can cause problems, e.g. with tests that are executed in a suite or re-init of the SDK.

💚 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

[github-actions]

	Fails
🚫	Please consider adding a changelog entry for the next release.

	Messages
📖	Do not forget to update Sentry-docs with your feature once the pull request gets approved.

Instructions and example for changelog

Please add an entry to CHANGELOG.md to the "Unreleased" section. Make sure the entry includes this PR's number.

Example:

## Unreleased

- Catch exceptions when closing integrations ([#3488](https://github.com/getsentry/sentry-java/pull/3488))

If none of the above apply, you can opt out of this check by adding #skip-changelog to the PR description.

Generated by 🚫 dangerJS against efb3601

[markushi]

Nice catch! LGTM

[github-actions]

Performance metrics 🚀

	Plain	With Sentry	Diff
Startup time	458.25 ms	534.84 ms	76.59 ms
Size	1.70 MiB	2.28 MiB	596.08 KiB

Baseline results on branch: feat/reuse-traces-sampler

Startup times

Revision	Plain	With Sentry	Diff
3d82da7	452.02 ms	509.15 ms	57.13 ms

App size

Revision	Plain	With Sentry	Diff
3d82da7	1.70 MiB	2.28 MiB	596.08 KiB