fix: don't use untagged on ksnap acr purge

[tallaxes]

Fixes #

Description

Don't use --untagged on ksnap acr purge, as it appears to be broken: Azure/acr-cli#131

How was this change tested?

• Re-deployed (updated) ksnap; will watch the next run

Does this change impact docs?

• Yes, PR includes docs updates
• Yes, issue opened: #
• No

Release Note

[coveralls]

Pull Request Test Coverage Report for Build 9603097293

Warning: This coverage report may be inaccurate.

This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

• For more information on this, see Tracking coverage changes with pull request builds.
• To avoid this issue with future PRs, see these Recommended CI Configurations.
• For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 97.758%

---

Totals
Change from base Build 9602285705:	0.0%
Covered Lines:	36285
Relevant Lines:	37117

---

💛 - Coveralls

[Bryce-Soghigian]

this will remove any image that is older than 30 days for snapshot images?

I also read about dry run we could use to test some of this if we wanted to add tests for this kind of thing.

--dry-run - Specifies that no data is deleted, but the output is the same as if the command is run without this flag. This parameter is useful for testing a purge command to make sure it does not inadvertently delete data you intend to preserve.

[tallaxes]

this will remove any image that is older than 30 days for snapshot images?

Yes

--dry-run

Yes, though I'd prefer to check the results of the actual execution instead; don't quite trust --dry-run at this point