fix(callback): Callback given to Sentry are execute safely

[krystofwoldrich]

📢 Type of change

• Bugfix
• New feature
• Enhancement
• Refactoring

📜 Description

These callback would crash the whole app if error is not caught.

I've thought about creating one safe() method that could wrap any callback, but for different callback the behaviour changes. Sometimes it makes sense to return undefined, sometimes defaults...

💡 Motivation and Context

Closes: #2499

💚 How did you test it?

Sample app.

📝 Checklist

• I reviewed submitted code
• I added tests to verify changes
• All tests passing
• No breaking changes

🔮 Next steps

[marandaneto]

So the safe methods are unit tested but not the functions that use them, if you remove the safeFactory wrapper when setting the before breadcrumb, tests are still green but the behavior is broken, I'd suggest also adding a test for the specific callbacks, just that they don't throw.

[marandaneto]

Awesome @krystofwoldrich

[github-actions]

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

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

- Callback given to Sentry are execute safely ([#2502](https://github.com/getsentry/sentry-react-native/pull/2502))

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 ba8502f