docs: add Integrations catalog reference page

[strawgate]

Adds a Reference → Advanced → Integrations page documenting the integrations catalog — one-click dashboards + alerts for Redis, PostgreSQL, MySQL, MongoDB, Elasticsearch, Memcached, RabbitMQ, Kafka, NGINX, and Apache.

Covers:

• What an integration delivers — a standard dashboard, live active alerts, the OTel Collector setup config, and on-demand detection.
• How to install — Detect and Install (whole catalog) or Install content (one pack); attaching a notification channel.
• The catalog — Available / Detected / Installed status, filters, search.
• Access from the MCP server (integration_list / integration_install).
• The available integrations.

Pairs with the platform PR that adds the feature (pydantic/platform#24849), which is gated behind the integrations_catalog flag — hold merge until the feature is enabled for users.

Catalog hero screenshot captured from a local stack; happy to re-shoot at a specific viewport if preferred.

[cubic-dev-ai]

No issues found across 3 files

Confidence score: 5/5

• Automated review surfaced no issues in the provided summaries.
• No files require special attention.

_{Re-trigger cubic}

[coderabbitai]

Warning

Review limit reached

@strawgate, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 1 minute

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: c298ac32-f3bc-4c37-9a08-f9f999c2b8a3

📥 Commits

Reviewing files that changed from the base of the PR and between 692ec02 and e65029a.

⛔ Files ignored due to path filters (1)

• docs/reference/advanced/images/integrations-catalog.png is excluded by !**/*.png

📒 Files selected for processing (2)

• docs/reference/advanced/integrations/index.md
• mkdocs.yml

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch docs/integrations-catalog

---

_{Comment @coderabbitai help to get the list of available commands.}