feat(settings): per-product Coverage / Include-Exclude / Enabled for SP cards

[cristim]

Background

PR #123 added four per-plan-type SP cards with independent term/payment defaults. Coverage, include/exclude filters, and enabled toggles still come from the global config to match the RI cards' behaviour.

If users want divergent coverage between Compute and SageMaker SP (e.g., 90% coverage on Compute SP but 50% on SageMaker SP because production utilisation differs), plumb the existing ServiceConfig.Coverage / ServiceConfig.IncludeTypes / ServiceConfig.Enabled fields to the four new rows and expose UI controls per card.

Acceptance criteria

• Each of the four per-plan-type SP cards exposes its own Coverage slider, Include/Exclude pickers, and Enabled toggle.
• Save path writes per-card values to the matching (aws, savings-plans-<type>) ServiceConfig row.
• Backend orchestrator already reads per-row values; no changes needed there.

References

• PR feat(settings): per-plan-type Savings Plans configuration (closes #22) #123 (closes ux(settings): SageMaker missing purchasing-defaults card #22)
• Plan §6.5 'Per-product Coverage / Include-Exclude / Enabled'

[cristim]

Verification

Original concern: Per #123 the four per-plan-type SP cards expose only Term and Payment; Coverage, Include/Exclude pickers, and Enabled toggle still come from the global config. Acceptance criteria: each of the four SP cards exposes its own Coverage slider, Include/Exclude pickers, and Enabled toggle; Save path writes per-card values to the matching (aws, savings-plans-<type>) ServiceConfig row.

What merged: PR #123 added the four cards (term + payment only). No subsequent PR is linked here that adds Coverage / Include-Exclude / Enabled controls per card.

Code state today (origin/feat/multicloud-web-frontend, frontend/src/settings.ts):

• SERVICE_FIELDS (lines 79-100) defines only termId + paymentId per row — no coverageId, no enabledId, no include/exclude IDs for any of the four savings-plans-{compute,ec2instance,sagemaker,database} services.
• Save handler (lines 2306-2327) builds the per-row ServiceConfig by spreading base ?? {} and overwriting only enabled: base?.enabled ?? true, term, payment, and coverage: base?.coverage ?? settings.default_coverage. Per-card Coverage/Enabled inputs would have to feed into this block; today they don't exist.
• index.html shows the per-SP-card controls under the Purchasing panel — only term + payment selects are present (no per-card coverage slider, no include/exclude pickers, no enabled toggle).

Recommendation: keep-open. Missing: per-card Coverage slider, per-card Include/Exclude (Types/Engines/Regions) pickers, and per-card Enabled toggle wired to write per-row ServiceConfig values, plus the SERVICE_FIELDS extension to carry the new control IDs and the matching tests.

[cristim]

Fixed in PR #580 (merged into feat/multicloud-web-frontend on 2026-05-22). Closing manually since GitHub does not auto-close on non-default-branch merges.