Enhance docker bootstrap to also build webpack, email images

[solebared]

Why

Currently, bin/dev/bootstrap only builds the app image and when we run bin/dev/serve or other dependent command, the webpack and email images are built. While there's value in building these 'just-in-time', i'd prefer bootstrap build all three images.

This will surface any issues when a user first sets up their docker env and subsequent commands will fire up more quickly.

Pre-Merge Checklist

• All new features have been described in the pull request
• New features have been documented, and the code is understandable and well commented
• All outstanding questions and concerns have been resolved
• Any next steps that seem like good ideas have been created as issues for future discussion & implementation

Testing

Tested locally but would love another set of eyes to verify.

Outstanding Questions, Concerns and Other Notes

• The dc function in bin/dev/bootstrap uses the $@ variable which seems to work but is new to me; is this an approprate use? Are there any gotcha's with it?

[indiebrain]

Tested locally but would love another set of eyes to verify.

LGTM, also ran through a local bin/dev/bootstrap and poked around the application, locally, myself as a "Yup, looks good over here too!". So I say 📦 🚀 🌔

I'll tease it here; I'm working on a change set that would allow the app and webpacker services share their cache layers; keeping the build process from doing the same things more than once - the "secret-sauce" utilizes Docker multi-stage builds. It's a non-trivial change to how the development Dockerfile currently works - will definitely be asking that folks have a run with it before I'd consider it "merge-able". I'll hopefully have a branch up in the next few days.

[indiebrain]

The dc function in bin/dev/bootstrap uses the $@ variable which seems to work but is new to me; is this an approprate use? Are there any gotcha's with it?

The $@ basically means "All arguments expanded positionally" and seems entirely appropriate here.

The only gotcha I can think of is sometimes $@ can expand in unexpected ways depending on if it's contained in a set of "s - I don't remember all the rules on when / why this happens, but something about word boundaries and how IFS is set comes to mind. I don't think that should pose a problem here, though. Figured I'd drop a few of my go-to bash resources as they're a much more authoritative source than my old and forgetful brain:

• https://devhints.io/bash
• https://wiki.bash-hackers.org/syntax/shellvars#special_parameters_and_shell_variables

[solebared]

Thanks for looking over this, and the bash links!