Make a CLI-only `DockerApiClient`

[bwateratmsft]

We need an implementation of DockerApiClient that uses CLI only. This will work better with a wider range of scenarios than the CLI + HTTP daemon through Dockerode + gRPC daemon. Plus it mostly removes the need to look up the Docker context during activation...

Potentially resolves:

• Dockerode features don't work with TCP daemon + certificates #2058
• Enable use of gpg-agent for Explorer view population #3295, "Failed to connect. Is Docker running?" in all docker views using a remote docker context #3590, Failed to connect. Is docker running? #3605
• Support rootless, daemonless podman inside WSL vscode-containers#51, Allow using podman instead of docker #1590, Add support for detecting podman. #3306, On a Mac, the extension keeps timing out when using Podman instead of Docker #3367, Need support for nerdctl vscode-containers#119
• No running container shows in container view after deploying image to ACI #2941, extension cannot list aci containers on linux #2933, No running container shows in container view after deploying image to ACI #3578
• [Codespaces] Fail to create a new ACI context in codespace environment #2391
• Don't communicate with docker until necessary #3475
• Remove notification to install Docker Desktop #3596
• Maybe The new created context start to move back and forth shortly in context view #2442

Related to #2977, #3281

[bwateratmsft]

I've noticed that com.docker.cli tends to be drastically faster than docker, though we would only want it to be used for background tasks (i.e. those where the user doesn't see the command line).