Separate competition setup from base provisioning

[slifty]

Lets allow a developer to choose which competitions to set up, using provisioning script tags.

This way someone who only needs a specific competition (or no competition) doesn't have to wait for everything.

This also will make it possible to set up new competitions without having to blow away the existing local build.

[slifty]

Instead of requiring a code change for setting up new competitions I think we should have a "setup_competition" provisioning script which takes in a named parameter -- maybe using https://stackoverflow.com/questions/14124234/how-to-pass-parameter-on-vagrant-up-and-have-it-in-the-scope-of-vagrantfile

We should also have a "run_etl" which also takes in a --competition=??? parameter

This way we can run something like vagrant provision --provision-with competition_setup --competition=Climate2030

I may discover that best practice is for things like etl happening inside the guest with a shell script instead of as a provisioning script, but at the very least I think competition setup makes sense as a named provisioning script