Compose v1 reaches end of life, and the alias that hid it

A shell alias mapping docker-compose to docker compose, added in 2021, which meant nobody noticed the old binary was still installed and still being used by two scripts.

$ type docker-compose
docker-compose is aliased to 'docker compose'

$ grep -rn 'docker-compose' deploy/ scripts/
  deploy/release.sh:41:  docker-compose -f prod.yml up -d
  scripts/reset-db.sh:8:  docker-compose exec db mysql

# scripts do not read interactive aliases. both had been
# running v1, which had been reading a v2 compose file
# with a `develop:` key it silently ignored.

An alias fixes the human path and leaves every non-interactive path on the old binary, which is the general shape of the problem — the fix looks complete because the place you test it is the place it works. Removing the binary rather than aliasing around it would have surfaced both scripts in 2021, at the cost of an afternoon that nobody had.