Add tests for the Native Bridges

[philipphofmann]

RNSentry.m has no tests. We could add a layer of abstraction, unit tests in Swift and run them in CI to validate its functionality.

[marandaneto]

also for Android, so I made it more generic, thanks.

[philipphofmann]

I wouldn't mind having two issues and / or two PRs so they get merged faster.

[bruno-garcia]

I don't disagree with the issue but worth mentioning that unit testing this has limited value as compared to an integration test. That's because this type is called by React Native (RCT_EXPORT_METHOD) and the type marshaling plays a role here too. Additionally, there's very little logic.

[marandaneto]

I believe some pieces could be unit tested but indeed, integration/e2e would play a bigger role.

[philipphofmann]

Integration tests make more sense because even if the unit tests are green the functionality could be broken because the underlying functionality changed.

[krystofwoldrich]

• iOS native tests added in chore(deps): update Cocoa SDK to v8.0.0 #2707
• Android native tests added in Add SentrySerialized to ReactNativeWritable convertor, load device context from sentry-java scope #3170