[Feat] Run custom automations across all repositories

[roomote-roomote]

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

What changed

• Add All repositories as a custom automation workspace target in the dashboard, web API, and automation management API.
• Persist org-wide scope separately from named environment IDs and launch those automation runs across active repositories.
• Pin org-wide launchable suggestions to a concrete repository, normalize repository names case-insensitively, persist only that repository's ID on each work item, resolve its matching environment, and preserve that routing metadata across supported chat surfaces.
• Reject missing, unknown, or inactive org-wide suggestion targets before tolerant preparation can silently discard proposed work.
• Document the org-wide automation behavior and large-workspace cost, and add focused persistence, launch, routing, API, and UI coverage.

Why this change was made

Team-wide automations can summarize work that spans several repositories. Requiring one named environment prevented those automations from inspecting the full organization and from creating correctly routed follow-up tasks.

Impact

Admins can select All repositories for a custom automation. The automation runs with organization-wide repository context, while each launchable suggestion stores only its owning repository scope and starts against the matching named environment when available. Repository-name casing is canonicalized, invalid targets return a clear error instead of silently losing the suggestion, and named environments that are deleted still fail closed rather than silently becoming org-wide.

[roomote-community]

No new code issues found. See task

• apps/api/src/handlers/tasks/submitTaskSuggestions.ts:1279 Org-wide current-thread suggestions without a target repository are rejected with a clear error, including Scan runs.
• apps/api/src/handlers/tasks/submitTaskSuggestions.ts:1514 Pinned org-wide suggestions persist and hash only their target repository ID.
• apps/api/src/handlers/tasks/submitTaskSuggestions.ts:1367 Org-wide current-thread suggestions with an unknown target repository are rejected before tolerant preparation can discard them.
• apps/api/src/handlers/tasks/submitTaskSuggestions.ts:294 Inactive repositories are excluded from explicit org-wide selections and rejected as targets.

_{Reviewed 1c2bdc7}

[roomote-roomote]

Fixed the repository-scope review comment in b8214b8. Each pinned suggestion now persists only its target repository ID while the full org-wide set remains available for validation. The branch is also current with develop. See task.

[roomote-roomote]

Addressed the additional review feedback through 9ca615e. Org-wide standard and scan suggestions now reject missing, unknown, stale, or inactive targets before tolerant preparation can silently discard work. The branch is current with develop, and the automation-only suggestion schema gate is preserved. See task.

[roomote-roomote]

Addressed the scope-safe advisor follow-ups in 1c2bdc7: repository names are matched case-insensitively and canonicalized before environment resolution and persistence, contradictory logging is removed, and docs explain the cost of preparing every active repository. Helper consolidation and a hard cap remain separate because they would change existing auto-act and product behavior. See task.