[reorg fix] Fix tracking consent link in Browser SDK setup partial

[jhgilbert]

🤖 Auto-generated fix for #38769.

@rphdbddog — the docs repo reorg created merge conflicts in your PR #38769. This is an auto-generated replacement with the file paths fixed; please use it instead of the original.

This PR replays the commits from #38769 with file paths translated to the post-reorg hugo/ layout. The original commits are preserved — same messages and authorship.

The original PR (#38769) will be closed in favor of this one.

Next steps:

1. Verify that this PR looks correct in the browser.
2. Remove the WORK IN PROGRESS label from this PR.
3. Wait for the standard docs team approval before merging. Optionally, you can check the 'ready for merge' checkbox below if you would like the docs team to merge it for you.

• Ready for merge

---

Original PR description:

What does this PR do? What is the motivation?

The "tracking consent value at initialization" link in the Browser SDK setup partial pointed at the browser section landing page (/real_user_monitoring/application_monitoring/browser), which contains no tracking consent content. It now points to the section that documents the trackingConsent initialization parameter, its granted / not-granted values, and the setTrackingConsent() API:

/real_user_monitoring/application_monitoring/browser/advanced_configuration/#user-tracking-consent

Merge instructions

This changes a shared partial (layouts/shortcodes/mdoc/en/sdk/setup/browser.mdoc.md), so the fix applies to every page that includes it:

• real_user_monitoring/application_monitoring/browser/setup/ (en)
• real_user_monitoring/application_monitoring/browser/setup/client/ (en, fr, es, ja, ko)
• client_sdks/setup/ (en)

Note that client_sdks/setup/ sits outside RUM, so an additional reviewer may be needed.

Merge readiness:

• Ready for merge

Additional notes

[rtrieu]

thank you!