chore(Mobile): Fixes tracing options casing, updates options

[kahest]

DESCRIBE YOUR PR

• Fixes options casing for all Mobile platforms
  fixes Android SDK: wrong casing for option keys #10237
• Removes outdated tracing-origins options (Android, KMP)
• Adds missing trace-propagation-targets option (RN)
• Adds whole section for Dart/Flutter

IS YOUR CHANGE URGENT?

Help us prioritize incoming PRs by letting us know when the change needs to go live.

• ideally June 11, latest June 20 :)

SLA

• Teamwork makes the dream work, so please add a reviewer to your PRs.
• Please give the docs team up to 1 week to review your PR unless you've added an urgent due date to it.
  Thanks in advance for your help!

PRE-MERGE CHECKLIST

Make sure you've checked the following before merging your changes:

• Checked Vercel preview for correctness, including links
• PR was reviewed and approved by any necessary SMEs (subject matter experts)
• PR was reviewed and approved by a member of the Sentry docs team

EXTRA RESOURCES

• Sentry Docs contributor guide

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
sentry-docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jun 10, 2024 8:07am

[codecov]

Bundle Report

Changes will decrease total bundle size by 14 bytes ⬇️

Bundle name	Size	Change
sentry-docs-server	7.45MB	3 bytes ⬇️
sentry-docs-edge-server	462.26kB	3 bytes ⬇️
sentry-docs-client	6.19MB	8 bytes ⬇️

[philipphofmann]

From the Apple standpoint, LGTM

[markushi]

LGTM!

[buenaflor]

looks good on kmp, dart/flutter 👍

[vivianyentran]

Left a suggestion. Thanks for updating!

[vivianyentran]

"Either this or must be defined to enable tracing."

Doesn't it default to 1 if these aren't defined?

[kahest]

only if enableTracing is set to true - then tracesSampleRate will be set to the recommended value of 1.0.

I know the wording for enableTracing that we copy-pasted and now have on all SDK docs is a bit confusing:

A boolean value, if true, transactions and trace data will be generated and captured. This will set the traces-sample-rate to the recommended default of 1.0 if traces-sample-rate is not defined

The default value is 0.0. The recommended value if you enable tracing is 1.0. We should probably re-word to something like

A boolean value that determines whether tracing is enabled and trace data will be generated and captured. This will set the traces-sample-rate to the recommended value of 1.0 if traces-sample-rate is not defined

OTOH there is an ongoing DACI to decide if we remove enableTracing altogether

[kahest]

Left a suggestion. Thanks for updating!

Thank you! I applied one suggestion. If we decide we want to update the wording on enableTracing, we should do that in a separate PR for all platforms at once (but I suggest we wait until the DACI is decided, see #10305 (comment)).