Handle complex types in NDK metadata

[lemnik]

Goal

Report all metadata added in the Java/Kotlin API in NDK events, rather than only types that can be directly manipulated from the C API.

Increase the maximum size of metadata section names and keys in NDK events to 64 bytes (including a null-terminator) instead of 32.

Design

Metadata that cannot be directly represented by the existing C model is now masked as an BSG_METADATA_OPAQUE_VALUE metadata value. These values are pre-encoded as JSON by the NDK plugin before being delivered as a string to the C layer.

The direct effect is:

• Strings will not be truncated to 63 characters, but will instead become OPAQUE if they are too long
• Maps and Lists will be included in NDK error reports (including any nested structures)

Testing

New unit tests and modified end-to-end tests ensure that no metadata is lost in a native event. The CXX signal test was modified to test the "clear" APIs within the C on_error handler, which requires async safety.

[bugsnagbot]

Android notifier sizes

Format	Size impact of Bugsnag (kB)	Size impact of Bugsnag when Minified (kB)
APK	1878.61	1629.83
arm64_v8a	659.85	414.09
armeabi_v7a	594.32	348.56
x86	733.56	487.8
x86_64	704.9	459.14

Generated by 🚫 Danger