fix(scopes): apply withScope data to events in globalHubMode

[markushi]

📜 Description

Sentry.withScope forks the current scope and makes it current, but Sentry.getCurrentScopes short-circuited to rootScopes when globalHubMode was enabled, so the fork was never read back. Everything set inside the callback was silently dropped.

Honour scopes that were explicitly made current, as long as they descend from the current rootScopes. Implicit forking stays suppressed. pushScope and popScope remain no-ops, since they are unbalanced.

💡 Motivation and Context

globalHubMode is on by default on Android, so this affected all Android users since 8.0.0.

• resolves: HTTP request payload and response body not captured in error events #5339
• resolves: JAVA-489

💚 How did you test it?

Unit tests in SentryTest.kt, run for globalHubMode both true and false. Verified they fail without the fix.

📝 Checklist

• I added GH Issue ID & Linear ID
• 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.
• Public API changes reviewed by another Mobile SDK team member or implemented according to the develop docs spec.

🔮 Next steps

Hybrid SDKs relying on withScope being a no-op under globalHubMode should be made aware.

🤖 Generated with Claude Code

[linear-code]

JAVA-489

[sentry]

📲 Install Builds

Android

🔗 App Name	App ID	Version	Configuration
SDK Size	io.sentry.tests.size	8.53.0 (1)	release

⚙️ sentry-android Build Distribution Settings

[sentry]

Bug: A TOCTOU race condition in getCurrentScopes() can cause it to return a stale Scopes object if Sentry.init() is called concurrently.
_{Severity: LOW}

Suggested Fix

To prevent the race condition, read the volatile variable rootScopes into a local variable at the start of the method. Use this local variable for both the isAncestorOf check and the subsequent return statement to ensure the same object is used for both operations.

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: sentry/src/main/java/io/sentry/Sentry.java#L122-L125

Potential issue: In `Sentry.getCurrentScopes()`, when `globalHubMode` is enabled, a
time-of-check to time-of-use (TOCTOU) race condition exists. The method reads the
`volatile` field `rootScopes` to perform a check with `isAncestorOf`, and then reads it
again for the return statement. If another thread calls `Sentry.init()` between these
two reads, `rootScopes` can be reassigned. This can cause `getCurrentScopes()` to return
a stale `Scopes` object from a previous SDK initialization, which is inconsistent with
the newly initialized SDK state. While the practical impact is low due to the narrow
race window and rare re-initialization, it is a concurrency flaw.

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