docs(python): Update Celery integration guide to the Quick Start format

[AmariahAK]

DESCRIBE YOUR PR

Closes #19036
(part of #18363)

What was the issue

The Celery integration guide (docs/platforms/python/integrations/celery/index.mdx)
still used the legacy "Getting Started" format, while the Python quick start guide
and its sibling guides now use the "Quick Start" format. It was missing a
Prerequisites section, numbered steps, feature toggles, and a Next Steps section.

Where

docs/platforms/python/integrations/celery/index.mdx (single file; crons.mdx untouched).

How it was fixed

• Added ## Prerequisites (folded in Celery 4.4.7+ / Python 3.6+) and removed the
  ## Supported Versions section and its legacy-SDK include.
• Wrapped the steps in `<StepConnector selector="h2" showNumbers=

{

true}>`.

• Converted ## Install to a SplitLayout with pip / uv / poetry tabs.
• Restructured ## Configure with OnboardingOptionButtons (error-monitoring,
  performance, profiling, metrics) and the features expandable; added
  ### Capturing Errors and ### Instrumenting Your App.
• Renamed ## Verify → ## Verify Your Setup with split-layout code samples and a
  "View Captured Data in Sentry" subsection.
• Converted the ## Options bullet list to SdkOption components.
• Added ## Next Steps; kept ## Distributed Traces (with the protocol v1/v2 note).

Why this approach

Self-contained: the guide reuses only includes already on master and inlines the
rest, so it builds cleanly without depending on any unmerged sibling-branch includes.

How to test locally

Run pnpm dev and open
http://localhost:3000/platforms/python/integrations/celery/ — confirm the numbered
steps, feature toggle buttons, split layouts, and SdkOption tables render.

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.):
• 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

[vercel]

@AmariahAK is attempting to deploy a commit to the Sentry Team on Vercel.

A member of the Team first needs to authorize it.