[Improve] Clarify Review Code copy on Automations

[roomote-roomote]

Opened on behalf of Bruno Bergher. Follow up by mentioning @roomote-roomote, in the web UI, or in Slack.

Related issue

Internal UX polish from product feedback on Automations.

Why this PR exists

• A maintainer explicitly invited this PR in the linked issue or discussion
• I am a maintainer / this is internal Roomote work

What changed

Automations page cleanup:

• Review Code copy/order/helpers
• Section layout: Source Code automations first, then Slack, managers, Meta automations
• Rolled back dynamic/configured provider badges after review: restored descriptor-based GitHub only / middot badges so empty intersections no longer look like full support

How it was tested

• vitest run AutomationsSettings.render.client.test.tsx
• Pre-push checks
• Manual browser check of /automations

Checklist

• The PR title follows the repo convention
• This PR is small and scoped to one change
• pnpm lint and pnpm check-types pass locally
• I added tests or included a clear manual validation note above
• I removed secrets, tokens, private keys, and customer data from code, logs, and screenshots
• If this change should appear in the changelog, I ran pnpm changeset

Screenshots

[roomote-roomote]

No new code issues found. See task

• apps/web/src/components/settings/automations/AutomationsSettings.tsx:2687 says automatic review covers “any new PRs,” but reviewerReviewAllPullRequestAuthors defaults to false and filters out PRs not opened by Roomote. Describe these as eligible/in-scope PRs so this toggle does not contradict the author-scope toggle below it.
• apps/web/src/components/settings/automations/AutomationsSettings.tsx:2712 says disabling draft reviews means Roomote will “only review PRs marked as ready,” but reviewDraftPrs controls automatic reviews only; an @-mention can still request review on a draft. Scope the helper to automatic reviews so users are not told that drafts are globally excluded.
• apps/web/src/components/settings/automations/AutomationsSettings.tsx:382 suppresses the capability badge when none of an automation's supported providers overlap the multiple configured providers. For example, a GitLab + Azure DevOps deployment shows no limitation badge on the GitHub-only Dependabot, CodeQL, and CI triage cards, which is the same visual signal as full support; render an explicit unsupported state instead of dropping the badge for an empty intersection.

_{Reviewed b9ff725}