Drop ENTRYPOINT in favor of CMD ["pass-cli"]

Every real caller (code.aneur.in/cloud/cloud's deploy workflows) runs a
mounted-in script against pass-cli, not bare pass-cli args, so an
ENTRYPOINT override was needed on every invocation. With no ENTRYPOINT,
`docker run this-image sh /script.sh` just replaces CMD directly.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

Dockerfile

@@ -3,10 +3,13 @@
 # (fcntl64, __res_init, ...) that Alpine's gcompat/libc6-compat don't shim,
 # so it can't run in e.g. the docker:cli image directly.
 #
-# ENTRYPOINT is pass-cli itself, so `docker run this-image <args>` behaves
-# like `pass-cli <args>`. Callers who need to run their own script against
-# pass-cli instead (login, fetch a note, parse it, etc.) override the
-# entrypoint: `docker run --entrypoint sh this-image /path/to/script.sh`.
+# No ENTRYPOINT -- just CMD ["pass-cli"]. `docker run this-image` runs bare
+# pass-cli; `docker run this-image <args>` replaces CMD entirely, so a
+# caller running their own script against pass-cli (login, fetch a note,
+# parse it, etc.) just does `docker run this-image sh /path/to/script.sh`
+# with no --entrypoint override needed. The cost: `docker run this-image
+# --version` doesn't work as shorthand -- write `docker run this-image
+# pass-cli --version` instead.
 
 FROM debian:bookworm-slim
 
@@ -26,4 +29,4 @@ RUN apt-get update \
 # No kernel keyring in a container -- store the session on disk instead.
 ENV PROTON_PASS_KEY_PROVIDER=fs
 
-ENTRYPOINT ["pass-cli"]
+CMD ["pass-cli"]