ref(android): Bound Nav3 argument payload size + report argument drop reasons

[0xadam-brown]

📜 Description

PR makes three refinements to how our Nav3 integration handles host-app provided arguments:

1. Limits the total argument characters sanitized from one back-stack update so large strings and stringified values cannot dominate navigation telemetry payloads or processing time.

2. Attaches a dropped reason marker when arguments are omitted for performance or safety reasons.

3. Reduces some of our argument limits in response to benchmark testing results.

💡 Motivation and Context

Addresses @markushi's helpful comment here + lets us incorporate findings from sample app benchmark testing.

addresses: JAVA-274

Screenshots

Back stack context

Breadcrumb

Span arguments

💚 How did you test it?

Unit tests.

📝 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

[sentry]

📲 Install Builds

Android

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

⚙️ sentry-android Build Distribution Settings

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

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

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

[0xadam-brown]

Replacing "arguments" key with "entry_arguments" in relevant unit tests to match updated implementation; otherwise unchanged.