OptionsGenerator regression: current regenerations break public APIs

[thomhurst]

Problem

Current automated CLI-options PRs still produce unapproved breaking public API changes. The API compatibility gate blocks auto-merge, but most affected members have no open issue tracking the required compatibility work.

Affected PRs and examples:

• [Automated] Update grype CLI Options #3895 Grype: removes public Command properties.
• [Automated] Update cargo CLI Options #3897 Cargo: renames positional record property DepVersion to Dep.
• [Automated] Update buildah CLI Options #3898 Buildah: removes Command and changes Pull.
• [Automated] Update docker CLI Options #3901 Docker: removes Provenance, Sbom, Models, Since, Until, NoTty, App, Wait, WaitTimeout, and QuietBuild.
• [Automated] Update pulumi CLI Options #3902 Pulumi: removes or renames positional/public members across multiple option types, including changing PulumiStackNewOptions construction.
• [Automated] Update trivy CLI Options #3903 Trivy: removes public Command properties.
• [Automated] Update kustomize CLI Options #3904 Kustomize: removes/renames existing methods, option records, and properties.
• [Automated] Update skopeo CLI Options #3907 Skopeo: changes CommandOptions from string? to IEnumerable<string>?.
• [Automated] Update flux CLI Options #3909 Flux: removes public Command properties and renames NameVersion to Name.

Helm/Pulumi/Podman optional-arity migrations are already tracked by #3777 and its pending fix #3859; this issue covers remaining compatibility regressions.

This is a recurrence of the class addressed by closed #3165. The scheduled-run umbrella #3910 records that the workflow failed, but not the member-level compatibility work.

Expected

• Preserve source and binary compatibility with obsolete forwarding aliases where semantics still match.
• Treat true removals/type replacements as explicit major-version decisions.
• Add common generator regression coverage for positional renames, removed scraped options, and scalar-to-collection changes.
• Regenerate or close affected PRs only after every API gate failure is resolved or explicitly approved.

[thomhurst]

Claimed. Auditing the merged generated-option API deltas against the pre-regeneration baseline, then restoring compatible forwarding aliases and adding generator regression coverage.