[Feature]: Connect-AzContainerRegistry should work without docker #30339

Description of the new feature

Given: we can build containers in .NET without docker
Given: we can use wslc (aka container) to build containers
Given: we use ACR for Bicep, Helm, and with the ORAS SDK for all sorts of other things that are not docker

As a DevOps engineer, I want Connect-AzContainerRegistry to populate the credential cache(s) without explicitly requiring docker.

Specifically, I knows that on Windows I can Set-Alias docker container (or wslc) to use that instead, and Connect-AzContainerRegistry will just work, but if I need oras instead, I might have to install the docker-credential-helper and Set-Alias docker oras

... but this trick doesn't work for helm, and the instructions are ridiculous, and really this can all be easily handled by Connect-AzContainerRegistry ;-)

Proposed implementation details (optional)

There are so many options here that I don't even know what the best one is.

The easy way (for users, at least) is to have a fallback. Check for podman or wslc or docker-credentialcred or docker-credential-wincred or docker-credential-pass or docker-credential-osxkeychain or whatever, and use those instead.

The easy way for you is to do what the Azure CLI does and check the environment variable DOCKER_COMMAND (or add a parameter -DockerCommand that falls back to $Env:DOCKER_COMMAND ?? 'docker' and use that instead.

But also, please handle helm according to your own instructions, if it's available.