Update setup-services.py to include images & volumes subtleties

[lsetiawan]

This PR makes --tear-down to also clean up images and volumes.

[emiliom]

Make this optional? Often I tear-down to not have active containers, but I'd like to have the ability to restart from the images w/o downloading everything (deploy) again.

[lsetiawan]

Just to add more details on this PR:

1. The issue of volumes blowing was because every time someone runs --deploy docker-compose will recreate the container, and specifically, the minio container will create NEW volume reference with a random id, which allocates space within the host machine. Now in the docker-compose.yaml. I've added a specific volume for the minio service called echopype_miniodata. This would then only create this volume one time, and it will not be recreated again, unless it gets deleted from running --tear-down.
2. Now --deploy can be paired with --no-pull, which skips pulling the latest images for both minio and http, by default it will pull.
3. Last, there's now --images flag that can be paired during --tear-down to also delete the docker images during tear down. By default, the images will be kept around. However, now the volumes for the docker containers will be removed during tear down.

[emiliom]

2. Now --deploy can be paired with --no-pull, which skips pulling the latest images for both minio and http, by default it will pull.

Perfect

3. Last, there's now --images flag that can be paired during --tear-down to also delete the docker images during tear down. By default, the images will be kept around. However, now the volumes for the docker containers will be removed during tear down.

Perfect

[emiliom]

I've looked at the changes in the PR and confirmed that your description of what has changed matches what we had discussed. I'm not going to run this locally to test it, though. I'm good with your own local tests and what happens once the PR is merged, next time the CI tests are run. I'll test it locally the next time I pull the merged changes and have to run the test suite.