Add per-option controls and structured cluster labels to the cloud provider dropdown

[morgan-wowk]

What

Extends the schema-driven Cloud Provider dropdown (TaskNode annotations editor) with per-option controls, richer structured option labels, and legacy-key resolution — no new dropdown, reusing the existing launcher_annotation_schemas-derived pipeline.

Per-option controls

• active — an option shows only when x-active !== false and its feature-flag-key (if any) is enabled.
• label ≠ value — the option's title gives a friendly display name while the value written to the backend stays the launcher key.
• deprecated — x-deprecated (+ optional x-deprecated-message) renders a small TriangleAlert icon with a tooltip beside the option, reusing the existing inline icon+tooltip primitive.

Structured provider / project / cluster labels

New x-provider / x-project / x-cluster schema fields flow onto AnnotationOption. When provider is present the dropdown item renders two lines — a primary provider line and a muted cluster · project secondary line — so an option can identify platform, project, and cluster at a glance while staying accessible and following the existing UI primitives.

To keep the collapsed control compact, the trigger no longer uses SelectValue; it renders a single-line summary (provider · cluster) from the selected option. Radix still tracks the value via each SelectItem's value, and the rich content remains inside ItemText for typeahead/a11y.

Legacy-key resolution

resolveLauncherKey maps a persisted cloud_provider value onto its current launcher key via an x-legacy-keys alias array on the canonical entry. getProviderSchema and the compute-resources editor resolve through it, so an overlay can rename a launcher key (e.g. google → a cluster id) without stranding existing pipelines that persisted the old value — they keep resolving to the renamed launcher instead of rendering an empty compute panel. When no alias applies the value passes through unchanged, so this is a no-op for current keys.

System / UX impact

• Both the v1 (AnnotationsSection) and v2 (ConfigurationSection) editors render through the same AnnotationsInput, so this covers both.
• Options with no x-provider (e.g. Davies) keep the existing single-line rendering.
• Purely additive schema fields; existing configs are unaffected.

Tests

AnnotationsEditor/utils.test.ts covers the parse layer: x-active gating (both mechanisms), label ≠ value, deprecated flag + message (launcher and enum paths), provider/project/cluster population, and resolveLauncherKey / getProviderSchema legacy-key resolution. pnpm typecheck, pnpm lint, pnpm test, pnpm format:check all pass.

[github-actions]

🎩 Preview

A preview build has been created at: add-eo9-cloud-provider-and-option-controls/2f4d0cb

[morgan-wowk]

• Add per-option controls and structured cluster labels to the cloud provider dropdown #2694 👈 (View in Graphite)
• master

This stack of pull requests is managed by Graphite. Learn more about stacking.