[Fix] Source control setup buttons are indistinguishable by provider

[roomote-roomote]

​Opened on behalf of @daniel-lxs. Follow up by mentioning @roomote-roomote, in the web UI, or in Telegram.

What changed

Each unconfigured source-control provider now has a distinct setup button name for assistive technology: “Set it up for GitHub”, “Set it up for GitLab”, “Set it up for Gitea”, “Set it up for Azure DevOps”, or “Set it up for Bitbucket Cloud”. The visible “Set it up” copy and existing setup interaction remain intact. Focused coverage checks all five names and the GitHub setup-form expansion.

Why this change was made

The authenticated Source Control Settings page previously exposed five indistinguishable “Set it up” buttons, making the intended provider ambiguous in assistive-technology navigation. Using the existing provider title keeps the change local to the shared provider block.

Impact

Screen-reader users can identify the provider before activating its setup action; the appearance and normal provider setup flow are unchanged. This is independent of #2400, which changes Session-level optional source-control connection and also touches the component; a rebase may be needed when either branch lands. The GitHub organization visibility work in #3044 is already merged and is not part of this change.

The focused web suite passed (22 tests), web package TypeScript, targeted ESLint/Oxlint/format checks, and the normal push hooks passed. On the real authenticated local settings page, the accessibility tree listed five distinct button names at desktop and mobile sizes; keyboard Enter on GitHub opened its setup form. Screenshots show the unchanged visible copy and layout and the expanded form, but cannot independently prove accessible names or keyboard input. No provider credentials were entered.

Screenshots

Before — desktop provider cards:

After — desktop provider cards:

Before — mobile provider cards:

After — mobile provider cards:

GitHub setup after keyboard activation — desktop and mobile:

[roomote-community]

No code issues found. See task

_{Reviewed d568c06}