fix: Bump Cocoa SDK for version 3

[bitsandfoxes]

Resolves #2367

We specifically want to bump to at least version 8.55.0 that includes the following change

Important

Xcode 26 no longer allows individual frameworks to contain arm64e slices anymore if the main binary doesn't contain them.
We have decided to split the Dynamic variant and Sentry-WithoutUIKitOrAppKit of Sentry into two variants:

• Sentry-Dynamic: Without ARM64e
• Sentry-Dynamic-WithARM64e: With ARM64e slice
• Sentry-WithoutUIKitOrAppKit: Without ARM64e
• Sentry-WithoutUIKitOrAppKit-WithARM64e: With ARM64e slice

If your app does not need arm64e, you don't need to make any changes.
But if your app needs arm64e please use Sentry-Dynamic-WithARM64e or Sentry-WithoutUIKitOrAppKit-WithARM64e from 8.55.0 so you don't have issues uploading to the App Store.

[linear]

COCOA-8 Fix flaky `test_applicationWithScenes`

[bitsandfoxes]

Regarding the Cursor comments: The method name initWithDict:didFailWithError: looks like an initializer (which would require [[Class alloc] init...]), but it's actually a factory method. This is a somewhat unusual naming convention, but it's intentional - it's part of Sentry's internal API.

[cursor]

Bug: Sentry Bridge Functionality Regression

Same issue as iOS version - SentryNativeBridgeSetExtra function behavior was changed from explicitly calling removeExtraForKey when value is NULL to always calling setExtraValue even with nil values. This could break the intended null-to-remove semantics expected by the C# layer.

 

[cursor]

Bug: Sentry Tagging Behavior Inconsistency

Same issue as iOS version for SentryNativeBridgeSetTag - behavioral change from explicit removal to always setting with potentially nil values.