feat(android-nav3): Android Nav3 integration

[0xadam-brown]

No code needs to be reviewed for this PR as it's already been reviewed in the PRs stacked on top of it and hasn't been modified since.

PR Stack (Android Nav3)

• feat(android-nav3): Android Nav3 integration #6128
• feat(android-nav3): [Android Nav3 1] Create the navigation3 module #6129
• feat(android-nav3): [Android Nav3 2] Model navigation routes #6130
• feat(android-nav3): [Android Nav3 3] Track navigation state transitions #6131
• feat(android-nav3): [Android Nav3 4] Introduce SentryNavEffect #6132
• feat(android-nav3): [Android Nav3 5] Make SentryNavEffect accessible to sample apps #6137

---

📜 Description

This is the collection branch for the Android Nav3 stack.

It carries no feature code itself. The implementation is split across the stacked PRs below so the
module scaffold, route modeling, observer layer, and Compose-facing effect can be reviewed
independently and merged forward through the branch chain before this collection branch is
squash-merged into main.

💡 Motivation and Context

Nav3 support is large enough that reviewing it as one PR would hide the architectural boundaries.
This collection branch gives us a stable top-level PR for the whole effort while the stack lands in
reviewable steps.

addresses: JAVA-274

⚠️ Does not make Nav3 support public

Note that this PR stack does not make Nav3 support public. (While API entry points use the public keyword, they remain @ApiStatus.Internal. The former is required so that we can post subsequent PRs for the Nav3 sample app.)

Once approved for public release, we'll remove the @ApiStatus.Internal annotations and include a proper CHANGELOG + cross references to official Sentry Nav3 docs.

💚 How did you test it?

This branch is intentionally empty apart from the collection commit. Each stacked PR contains its
own verification details.

📝 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

• Create PRs for the Nav3 sample app.
• Remove the @ApiStatus.Internal annotations from SentryNavEffect, SentryNavOptions, RouteNameExtractor, and RouteArgumentsExtractor once we're ready to release publicly + add an appropriate CHANGELOG entry + publish the module via craft (link).
• sentry-docs

#skip-changelog

[github-actions]

	Messages
📖	Do not forget to update Sentry-docs with your feature once the pull request gets approved.

Generated by 🚫 dangerJS against a4d1f06

[sentry]

📲 Install Builds

Android

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

⚙️ sentry-android Build Distribution Settings

[cursor]

Cursor Bugbot has reviewed your changes and found 2 potential issues.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

Want reviews to match your repository better? Bugbot Learning can learn team-specific rules from PR activity. A team admin can enable Learning in the Cursor dashboard.

^{Reviewed by Cursor Bugbot for commit ecb6243. Configure here.}

[0xadam-brown]

Pushes were me getting my clanker to add #6137 to the commit list. All code is identical to what was previously reviewed + approved.

[0xadam-brown]

Re-ran apiDump to pick up the SentryNavOptions.toString() method my clanker missed when rebasing. Otherwise no changes.