docs(js): remove Connect guide and integration (no longer supported)

[mydea]

DESCRIBE YOUR PR

Stacked PR. Part of the JavaScript guide-categories series (#19492 → #19513). Depends on #19512; review/merge bottom-up.

The Sentry JavaScript SDK no longer supports the Connect framework, so remove its guide and the Connect integration page, and strip javascript.connect from every support list across the docs.

• Delete guides/connect/ and configuration/integrations/connect.mdx.
• Remove javascript.connect from 46 frontmatter/JSX support lists.
• Repoint the two product getting-started samples from platform="javascript.connect" to javascript.node.
• Redirect /platforms/javascript/guides/connect/* → the Node guide (Connect's former fallbackGuide).

IS YOUR CHANGE URGENT?

Help us prioritize incoming PRs by letting us know when the change needs to go live.
Select exactly one option. For deadlines, replace YYYY-MM-DD with the due date. You can update this information later by editing the PR description.

• Urgent deadline (GA date, etc.): YYYY-MM-DD
• Other deadline: YYYY-MM-DD
• No deadline: 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 supplied a deadline.

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

---

🤖 Generated with Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
develop-docs	Ready	Preview	Sep 22, 2026 1:25pm UTC
sentry-docs	Error		Sep 22, 2026 1:25pm UTC

[sentry]

Bug: Hard-coded links in the metrics and logs getting-started guides point to old connect paths. The new redirect rule sends users to non-existent pages, causing a 404 error.
_{Severity: HIGH}

Suggested Fix

Update the hard-coded url props in /docs/product/metrics/getting-started/index.mdx and /docs/product/logs/getting-started/index.mdx. The links should point to the correct, existing pages within the /platforms/javascript/guides/node/ path, or be removed if no equivalent guide exists.

Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent. Verify if this is a real issue. If it is, propose a fix; if not, explain why it's
not valid.

Location: redirects.js#L590-L593

Potential issue: The pull request introduces a redirect from
`/platforms/javascript/guides/connect/:path*` to
`/platforms/javascript/guides/node/:path*`. However, it fails to update hard-coded links
in two getting-started guides: `/docs/product/metrics/getting-started/index.mdx` and
`/docs/product/logs/getting-started/index.mdx`. These links still point to the old
`connect` paths. When a user clicks them, the redirect rule correctly fires but sends
them to non-existent pages (`/platforms/javascript/guides/node/metrics/` and
`/platforms/javascript/guides/node/logs/`), resulting in a 404 error and a broken user
flow.

_{Did we get this right? 👍 / 👎 to inform future reviews.}