Reduce/remove need for manual dev env docker-compose image tag management #216
Description
In the dev environment docker-compose configuration, some services are always live against the source code on disk (and service based on the node-dev image) and some only refresh when the images rebuild (requiring devs to kill the docker env and either bump the respective image tag in docker-compose.dev.yaml or manually rm the previous image build; ideally they bump the tag so other dev's local docker images are busted, but even that gets clunky if multiple live branches increment the tags to the same numbers).
I could force those images to rebuild every time the docker compose env is launched, but that might be too painful. Could build the equivalent for the node-dev image for the python and r services, but that's a maintenance burden. Hm.