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

📜 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

💚 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

Merge the stack from [Android Nav3 4] back down to [Android Nav3 1] with merge commits, then
squash-merge this collection branch into main.

#skip-changelog