chore(deps): bump providers/azure past 58c25f0 after #475 merges #654

Summary

cloud-commitments-go PR #207 (fix(azure): report only savings plans billed to the subscription) merged to main as 58c25f0 (pseudo-version v0.0.0-20261007133317-58c25f04c49b). Fleet PR #475 pins providers/azure at e24345c (the #218 run-rate fix), which predates 58c25f0 — so after #475 merges, the azure pin still lacks the #207 fail-closed inventory change. Azure-pin changes are frozen while #475 is in flight (orchestrator deconfliction, 2026-10-07), so this issue tracks the follow-up bump.

Consumer impact audit (done 2026-10-07, no code change needed)

• GetExistingCommitments for Azure savings plans can now return an error where it previously returned a silently partial list (billing-account/management-group scopes and malformed rows hard-error).
• This platform has zero non-test callers of GetExistingCommitments (repo-wide grep; only test mocks implement it). The only error-ambiguous consumer, pkg/recfilter.DuplicateChecker.AdjustRecommendationsForExisting (returns all recs as passed alongside the error), has no callers in this repo or inside the pinned modules.
• Duplicate-purchase protection for Azure savings plans rests on the module's PUT order-alias idempotency (services/savingsplans/client.go: "PUT with a previously-used name returns the existing order alias"), which is unaffected by the fix(ci): database-migration.yml discards the real terraform error when reading the DB endpoint #207 change.

Expected outcome

After #475 merges and the pin freeze lifts, bump github.com/LeanerCloud/cloud-commitments-go/providers/azure to v0.0.0-20261007133317-58c25f04c49b or later (per-module pin; do not move providers/aws or providers/gcp to the same SHA). Build and run the azure-tagged tests; no caller changes are expected to be required per the audit above.

References

• Fleet relay: cloud-commitments-go#207 merged as 58c25f0
• Pin landing in: PR fix(azure): roll out reservation fixes and preserve exchange scopes #475 (closes chore(deps): pin providers/azure at or after cloud-commitments-go e24345c (Azure monthly run-rate fix) #650); supersedes fix(deps): pin azure provider at cloud-commitments-go e24345c run-rate fix #651 and chore(deps): pin azure provider at the run-rate fix merge (cloud-commitments-go#218) #652
• Related: fix(aws): exclude uninitialized Fargate tasks from ALB readiness #647 (AWS readiness), which is independent of pins

Severity

Low — no caller impact in this repo; this is a tracking chore for the pin bump.