chore(deps): update Native SDK to v0.10.0

[github-actions]

Bumps packages/flutter/scripts/update-native.sh from 0.9.1 to 0.10.0.

Auto-generated by a dependency updater.

Changelog

0.10.0

Breaking changes:

• By using transactions as automatic trace boundaries, transactions will, by default, no longer be part of the same singular trace. This is not the case when setting trace boundaries explicitly (sentry_regenerate_trace() or sentry_set_trace()), which turns off the automatic management of trace boundaries. (#1270)
• Change transaction sampling to be trace-based. This does not affect you when transactions are used for automatic trace boundaries (as described above), since every transaction is part of a new trace. However, if you manage trace boundaries manually (using sentry_regenerate_trace()) or run the Native SDK inside a downstream SDK like the Unity SDK, where these SDKs will manage the trace boundaries, for a given traces_sample_rate, either all transactions in a trace get sampled or none do with probability equal to that sample rate. (#1254)
• Moved Xbox toolchains to an Xbox-specific repository sentry-xbox. You can request access to the repository by following the instructions in Xbox documentation. (#1329)

Features:

• Add sentry_clear_attachments() to allow clearing all previously added attachments in the global scope. (#1290)
• Automatically set trace boundaries with every transaction. (#1270)
• Provide sentry_regenerate_trace() to allow users to set manual trace boundaries. (#1293)
• Add Dynamic Sampling Context (DSC) to events. (#1254)
• Add sentry_value_new_feedback and sentry_capture_feedback to allow capturing User Feedback. (#1304)
  • Deprecate sentry_value_new_user_feedback and sentry_capture_user_feedback in favor of the new API.
• Add sentry_envelope_read_from_file, sentry_envelope_get_header, and sentry_capture_envelope. (#1320)
• Add (u)int64 sentry_value_t type. (#1326)

Meta:

• Marked deprecated functions with SENTRY_DEPRECATED(msg). (#1308)

Internal:

• Crash events from Crashpad now have event_id defined similarly to other backends. This makes it possible to associate feedback at the time of crash. (#1319)