Upgrade to Caddy docker image 1.X

We are currently using the Caddy docker image 0.11.5. The most recent version of the Caddy docker image is 1.0.3. An attempt to run 1.0.3 on beta.nepalmap.org suggests there may be some adjustment that needs to be made in order to run 1.X.

This is what the error looks like when the caddy server tries to start
```bash
caddy_1 | timeout: unrecognized option: t
caddy_1 | BusyBox v1.30.1 (2019-06-12 17:51:55 UTC) multi-call binary.
caddy_1 |
caddy_1 | Usage: timeout [-s SIG] SECS PROG ARGS
caddy_1 |
caddy_1 | Runs PROG. Sends SIG to it if it is not gone in SECS seconds.
caddy_1 | Default SIG: TERM.
caddy_1 | wait-for-it: timeout occurred after waiting 30 seconds for web:8000
caddy_1 | wait-for-it: strict mode, refusing to execute subprocess
caddy_1 | timeout: unrecognized option: t
caddy_1 | BusyBox v1.30.1 (2019-06-12 17:51:55 UTC) multi-call binary.
caddy_1 |
caddy_1 | Usage: timeout [-s SIG] SECS PROG ARGS
caddy_1 |
caddy_1 | Runs PROG. Sends SIG to it if it is not gone in SECS seconds.
caddy_1 | Default SIG: TERM.
caddy_1 | wait-for-it: timeout occurred after waiting 30 seconds for web:8000
caddy_1 | wait-for-it: strict mode, refusing to execute subprocess
caddy_1 | timeout: unrecognized option: t
caddy_1 | BusyBox v1.30.1 (2019-06-12 17:51:55 UTC) multi-call binary.
caddy_1 |
caddy_1 | Usage: timeout [-s SIG] SECS PROG ARGS
caddy_1 |
caddy_1 | Runs PROG. Sends SIG to it if it is not gone in SECS seconds.
caddy_1 | Default SIG: TERM.
caddy_1 | wait-for-it: timeout occurred after waiting 30 seconds for web:8000
caddy_1 | wait-for-it: strict mode, refusing to execute subprocess
caddy_1 | timeout: unrecognized option: t
caddy_1 | BusyBox v1.30.1 (2019-06-12 17:51:55 UTC) multi-call binary.
caddy_1 |
caddy_1 | Usage: timeout [-s SIG] SECS PROG ARGS
caddy_1 |
caddy_1 | Runs PROG. Sends SIG to it if it is not gone in SECS seconds.
caddy_1 | Default SIG: TERM.
caddy_1 | wait-for-it: timeout occurred after waiting 30 seconds for web:8000
caddy_1 | wait-for-it: strict mode, refusing to execute subprocess
caddy_1 | timeout: unrecognized option: t
caddy_1 | BusyBox v1.30.1 (2019-06-12 17:51:55 UTC) multi-call binary.
caddy_1 |
caddy_1 | Usage: timeout [-s SIG] SECS PROG ARGS
caddy_1 |
caddy_1 | Runs PROG. Sends SIG to it if it is not gone in SECS seconds.
caddy_1 | Default SIG: TERM.
caddy_1 | wait-for-it: timeout occurred after waiting 30 seconds for web:8000
caddy_1 | wait-for-it: strict mode, refusing to execute subprocess
caddy_1 | timeout: unrecognized option: t
caddy_1 | BusyBox v1.30.1 (2019-06-12 17:51:55 UTC) multi-call binary.
caddy_1 |
caddy_1 | Usage: timeout [-s SIG] SECS PROG ARGS
caddy_1 |
caddy_1 | Runs PROG. Sends SIG to it if it is not gone in SECS seconds.
caddy_1 | Default SIG: TERM.
caddy_1 | wait-for-it: timeout occurred after waiting 30 seconds for web:8000
caddy_1 | wait-for-it: strict mode, refusing to execute subprocess
nepalmapfederal_caddy_1 exited with code 1
```

Start by locating the Caddy image reference and the wait-for-it invocation in the deployment configuration, then reproduce the reported startup failure with image 1.0.3. Check the BusyBox timeout error while testing the beta.nepalmap.org deployment; done means Caddy starts successfully and the web:8000 check completes without repeated timeouts.

Written by the indexing model from the issue text.