Increase default level of feedback/confirmation in dry-run of destructive commands

[stishkin]

When running onefuzz jobs containers delete <job-id> the --dryrun flag does not indicate whether the containers have already been deleted. It could be useful if it did. This may require tracking more container metadata, or making additional queries.

AB#35966

[mgreisen]

The level of feedback provided by the fix for #1264 is enough for now.

[ranweiler]

Reopening for discussion, since this feature request wasn't actually addressed.

[ranweiler]

Motivating use case from an end-user:

My goal is understanding: "what has already been deleted?".

My steps were:

1. I wanted to remove the containers associated with a job id.
2. I ran --dryrun to see what would get deleted.
3. That looked ok, so I ran delete without --dryrun.
4. Then I re-ran --dryrun to see what the status was. There it was again printing "would be deleted", suggesting that the containers had not, in fact, been deleted.
5. So I re-ran delete without --dryrun, and this time it did print "already deleted", suggesting that the containers had, verily, been deleted already.
6. And there I understood that --dryrun does not check the status of the containers before listing them as deletable.