Fix sentry unwrap nullable macro type mismatch

[philprime]

📜 Description

Corrected the application of the SENTRY_UNWRAP_NULLABLE macro in SentryProfiler.mm to directly unwrap configurationFromLaunch.profileOptions.

💡 Motivation and Context

The SENTRY_UNWRAP_NULLABLE macro was incorrectly attempting to unwrap configurationFromLaunch (type SentryProfileConfiguration *) as SentryProfileOptions, then accessing .profileOptions on the result. This type mismatch could lead to compilation errors or runtime crashes. The change ensures the macro unwraps configurationFromLaunch.profileOptions (type SentryProfileOptions *) directly, resolving the issue.

💚 How did you test it?

Verified that no other instances of the incorrect SENTRY_UNWRAP_NULLABLE(SentryProfileOptions, configurationFromLaunch) remained and that other related usages were already correct.

📝 Checklist

You have to check all boxes before merging:

• I added tests to verify the changes.
• No new PII added or SDK only sends newly added PII if sendDefaultPII is enabled.
• I updated the docs if needed.
• I updated the wizard if needed.
• Review from the native team if needed.
• No breaking change or entry added to the changelog.
• No breaking change for hybrid SDKs or communicated to hybrid SDKs.

---

[cursor]

Cursor Agent can help with this pull request. Just @cursor in comments and I'll start working on changes in this branch.
_{Learn more about Cursor Agents}

[github-actions]

	Fails
🚫	Please consider adding a changelog entry for the next release.

Instructions and example for changelog

Please add an entry to CHANGELOG.md to the "Unreleased" section. Make sure the entry includes this PR's number.

Example:

## Unreleased

- Fix sentry unwrap nullable macro type mismatch ([#5890](https://github.com/getsentry/sentry-cocoa/pull/5890))

If none of the above apply, you can opt out of this check by adding #skip-changelog to the PR description or adding a skip-changelog label.

Generated by 🚫 dangerJS against 78c257b