aliasing chalk to docker breaks a bunch of similar docker commands

running chalk with the config:
```
default_command: "docker"
```
and then aliasing `chalk` to `docker` so that docker is always run via chalk will break multiple docker commands that chalk _thinks_ is a chalk command but doesn't recognize.

For example `exec`:
```
liming@system76-pc:~/workspace/chalk$ docker exec -it alpine sh -c "echo a && echo b"
error: This chalk instance has no configured process to exec.
error: At the command line, you can pass --exec-command-name to set the program name (PATH is searched).
error: Add extra directories to search with --exec-search-path.
error: In a config file, set exec.command_name and/or exec.search_path
```
Or `login`:
```
liming@system76-pc:~/workspace/chalk$ docker login
warn: Code signing not initialized. Run `chalk setup` to fix.
Error: Cannot perform an interactive login from a non TTY device
```
`help` kicks the user into the chalk help output instead of the docker help output, which may not be what they're looking for, and `version` gives the chalk version instead of the docker version

Aliasing is what we recommend our users do when running docker with chalk, so it's likely that someone doing this will run into a whole bunch of unexpected issues when trying to use docker "normally".

Start by reproducing the documented default_command configuration and chalk-to-docker alias, then check how exec, login, help, and version are dispatched. The issue names no source files or tests, so trace the CLI entry point and command handling for these examples. Done means normal Docker commands no longer trigger Chalk behavior unexpectedly when invoked through the alias.

Written by the indexing model from the issue text.