feat(flags): Consolidate feature flags pull requests

[cmanallen]

DESCRIBE YOUR PR

Tell us what you're changing and why. If your PR resolves an issue, please link it so it closes automatically.
Simplifies deployment and review by putting all the documentation together in a shared PR.

IS YOUR CHANGE URGENT?

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

• Urgent deadline (GA date, etc.): 2024/12/02
• Other deadline:
• None: Not urgent, can wait up to 1 week+

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

LEGAL BOILERPLATE

Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. and is gonna need some rights from me in order to utilize my contributions in this here PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms.

EXTRA RESOURCES

• Sentry Docs contributor guide

[ryan953]

Structurally I think we're set.

Links all look good and work. And the large sections of each page make sense to me in terms of:

• what content is on each page
• the sidebar link order and organization (it's messy).

[ryan953]

Everything basically links back to the Home > Product Walkthrough > Explore > FF page, so in my mind that's the starting point

Then you've got the Issues > Issue Details walkthrough page sort of side quest, which links back to explore

Setup wise there are two paths: Eval Tracking & Change Tracking

Eval Tracking:
From the Explore page we link to each SDK landing page: Python & JS. The landing pages also pivot back to explore for Change Tracking.
Then from each landing page we link into the provider specific pages; those provider pages pivot uses back to the Explore page too

Change Tracking:
Just LD change tracking right now, but that page has quick links to the SDK pages for LD. Instead of linking to the Explore page it links to that Issues Details side-quest page.