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

[github-actions]

Bumps modules/sentry-native from 0.16.6 to 0.16.8.

Auto-generated by a dependency updater.

Changelog

0.16.8

Features:

• Add sentry_options_set_initial_scope for configuring scope data before the crash backend is started, including out-of-process crash handlers. (#2087)

Fixes:

• Respect independent rate limits for feedback, logs, metrics, and attachments instead of dropping them during error backoff. (#2109)

Thank you:

• nathan-white-mojang

0.16.7

Important:

This version was accidentally released from master and includes breaking changes intended for 0.17. It is superseded by 0.16.8, which restores compatibility with 0.16.6 and includes the intended hotfixes.

See https://github.com/getsentry/sentry-native/releases/tag/0.16.7 for the original changelog.

[sentry]

Bug: The C# code unconditionally calls the native function sentry_options_set_enable_logs, which was removed in the updated sentry-native submodule, silently disabling native crash reporting.
_{Severity: CRITICAL}

Suggested Fix

The P/Invoke call to sentry_options_set_enable_logs and its declaration in SentryNativeBridge.cs should be removed, as the underlying native function no longer exists. The feature it controlled was a no-op in recent versions anyway.

Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent. Verify if this is a real issue. If it is, propose a fix; if not, explain why it's
not valid.

Location: modules/sentry-native#L1

Potential issue: The `sentry-native` submodule was updated, which removed the exported
function `sentry_options_set_enable_logs`. However, the C# code in
`SentryNativeBridge.cs` still attempts to call this function via P/Invoke. This will
cause an `EntryPointNotFoundException` at runtime. While a `try-catch` block in
`SentryNative.Configure()` prevents an application crash, it also silently disables
native crash reporting on all supported platforms (Windows, macOS, Linux, iOS, and
Android). This means users will believe native crash reporting is active when it is not,
leading to a loss of critical crash data.

_{Did we get this right? 👍 / 👎 to inform future reviews.}

[jpnurmi]

Superceded by #2862