fix(cli): continue multi-item deletes after failures

[grs]

Summary

CLI delete commands that accept multiple targets (sandbox delete, provider delete, provider profile delete) previously aborted on the first failing entry, leaving the remaining requested items untouched. This makes multi-item deletes fail-soft: each entry is attempted, per-item failures are reported to stderr as they happen, and the command exits with a single aggregated error once every requested deletion has been attempted.

Related Issue

Fixes #3102

Changes

• sandbox_delete, provider_delete, and provider_profile_delete now collect per-item failures and continue instead of returning on the first error. Each failure is printed to stderr; the aggregated error is returned at the end.
• documentation updated to include example of multi-delete and describe the fail-soft behaviour

Testing

• mise run pre-commit passes
• Unit tests added/updated
• E2E tests added/updated (if applicable)

Checklist

• Follows Conventional Commits
• Commits are signed off (DCO)
• Architecture docs updated (if applicable)

[copy-pr-bot]

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

[johntmyers]

gator-agent

PR Review Status

This focused CLI fix matches accepted issue #3102: all requested sandbox, provider, and provider-profile deletions are attempted, failures are aggregated, and the user-facing behavior is documented. The initial code-only review found no blocking defects.

Blocking findings:

• No blocking findings remain

Carried findings:

• None

Non-blocking suggestions:

• None

Gator metadata

• Validation: Project-valid because it implements accepted issue #3102 as a concentrated CLI correctness fix.
• Docs: Relevant Fern pages under docs/ document the multi-delete behavior; navigation changes are not needed because the existing pages remain in place.
• Checks: Current-head Branch Checks and Helm Lint are not yet dispatched; DCO and vouch are green.
• E2E: test:e2e is required because sandbox deletion lifecycle behavior changes; dispatch is pending.
• Head SHA: 1cdf6c5f1a8fbb89beccccda8738d35e693ddfe7
• Base SHA: 5b925dd8afba6ba558e93803656e680b744769d7
• Merge base SHA: 5b925dd8afba6ba558e93803656e680b744769d7
• Patch ID: f6cfeb69a92205f1e408605063a995f9e9cf26f3
• Gator payload: 8
• Review mode: initial
• Previous reviewed SHA: none
• Review budget exhausted: no
• Maintainer decision required: no
• Next state: gator:in-review

[github-actions]

Label test:e2e applied, but pull-request/3111 does not exist yet. A maintainer needs to comment /ok to test 1cdf6c5f1a8fbb89beccccda8738d35e693ddfe7 to mirror this PR. Once the mirror exists, re-apply the label or re-run Branch E2E Checks from the Actions tab.

[johntmyers]

/ok to test 1cdf6c5

[johntmyers]

gator-agent

Monitoring Complete

Monitoring is complete because this PR has merged.

Final status: the current head was reviewed with no blocking findings, required checks including E2E passed, and maintainer approval was present before merge.

I removed the active gator:* label because there is nothing left for gator to monitor on this PR.

Gator metadata

• Head SHA: 1cdf6c5f1a8fbb89beccccda8738d35e693ddfe7
• Gator payload: 8
• Final state: merged