docs: add try_catch processor to Cloud

[JakeSCahill]

Summary

Adds the cloud-docs page for the try_catch processor, which is cloud-supported as of Redpanda Connect 4.98.0 but was missing a cloud-docs page (flagged by the auto-docs generation run and CodeRabbit on redpanda-data/rp-connect-docs#452).

• Single-sourced stub at modules/develop/pages/connect/components/processors/try_catch.adoc (includes connect:components:processors/try_catch.adoc[tag=single-source])
• Nav entry in alphabetical position (after try)
• What's New entry under June 2026, following the string_split precedent (docs: add string_split processor to Cloud #547)

Dependency

⚠️ Draft until redpanda-data/rp-connect-docs#452 merges. The cloud-docs playbook builds rp-connect-docs from main, so the include target (try_catch.adoc source page) does not exist yet and the preview will fail to resolve it until that PR lands. Mark ready for review after #452 merges.

🤖 Generated with Claude Code

[netlify]

✅ Deploy Preview for rp-cloud ready!

Name	Link
🔨 Latest commit	f703541
🔍 Latest deploy log	https://app.netlify.com/projects/rp-cloud/deploys/6a4d03c676c3f300081cdf36
😎 Deploy Preview	https://deploy-preview-630--rp-cloud.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 15 minutes

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

Run ID: 8ef8d7b2-1729-46a4-812a-ef5ab4bcde01

📥 Commits

Reviewing files that changed from the base of the PR and between dca51de and f703541.

📒 Files selected for processing (3)

• modules/ROOT/nav.adoc
• modules/develop/pages/connect/components/processors/try_catch.adoc
• modules/get-started/pages/whats-new-cloud.adoc

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch docs/add-try-catch-processor

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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