Add -Force parameter on any ConfirmImpact="High" cmdlets

[TylerLeonhardt]

Feature Idea Summary

We should have a -Force to skip over confirmation since -Confirm:$false is tedious.

Feature Idea Additional Details

Take a look at @KevinMarquette's awesome blog post on implementing whatif/confirm/force:
https://powershellexplained.com/2020-03-15-Powershell-shouldprocess-whatif-confirm-shouldcontinue-everything/#implementing--force

Requested Assignment

I'm just suggesting this idea at this time.

[HowardWolosky]

I had brought this up initially when the idea was being introduced in #145. I think that doing this makes sense, as -Force was my natural instinct for how to avoid the prompting before learning about -Confirm:$false (which is why I've been enforcing having a -Confirm:$false example with every command that is ConfirmImpact='High'.

I like that by having both, there's the "standard" way that has built-in support by PowerShell, but also the more "natural" way that people might be inclined to initially try.

This wouldn't be a breaking change, so this seems reasonable for someone to tackle right away if they're interested.

[giuseppecampanelli]

I'll tackle this 😄

[HowardWolosky]

@themilanfan - it's yours. Thanks so much!