[Automated] Update gcloud CLI Options

[thomhurst]

Summary

This PR contains automatically generated updates to gcloud CLI options classes.

The generator scraped the latest CLI help output from the installed tool.

Changes

• Updated options classes to reflect latest CLI documentation
• Added new commands if any were detected
• Updated option types and descriptions

Verification

• Solution builds successfully

---

🤖 Generated with ModularPipelines.OptionsGenerator

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Metrics 0 complexity

Metric	Results
Complexity	✅ 0 (≤ 20 complexity)

View in Codacy

_{NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.}

[claude]

Code Review

PR: [Automated] Update gcloud CLI Options
Change: 1 file, +1/-1 lines

---

Summary

This automated PR makes a single change: updating the GeneratedAt timestamp in AssemblyInfo.Generated.cs from 2026-04-19T04:08:20Z to 2026-04-26T03:45:21Z. No actual gcloud CLI options were added, removed, or modified.

---

Issue: Generator creates PRs for timestamp-only changes

The options generator ran, found zero changes to the actual CLI options, yet still created a pull request — solely to advance the GeneratedAt timestamp. This is noise:

• It wastes CI resources (builds, checks, code coverage uploads) for a no-op change.
• It floods the PR list with trivially mergeable but valueless PRs.
• Reviewers must open each PR to determine whether anything substantive changed.

Why this matters architecturally: The GeneratedAt timestamp serves as a diagnostic ("when was this last regenerated?"), but that diagnostic shouldn't drive PR creation. A PR should represent a meaningful change to the codebase.

Suggested approaches (pick one):

1. Skip PR creation when nothing changed — After generation, diff the output against HEAD. If the only modified file is AssemblyInfo.Generated.cs (i.e. only the timestamp changed), abort without opening a PR. This is the most impactful fix.

2. Move the timestamp out of source control — Store GeneratedAt in a sidecar file (e.g. gcloud.generated-at) that is git-ignored, so it never appears in diffs. The timestamp stays available for diagnostics without polluting commits.

3. Coarsen the timestamp granularity — Record only the date (e.g. 2026-04-26) rather than milliseconds. This won't eliminate the problem but reduces spurious weekly PRs to at most one per day, making it easier to spot genuine gaps.

Option 1 is the cleanest: the generator already knows what it generated, so checking whether anything substantive changed before creating a PR is straightforward.

---

The automated tooling and the assembly metadata pattern are both well-designed; this is a narrow but worth-fixing workflow issue.