Deployments should be programmatically selectable about runway

[ITProKyle]

You mention both deployments and modules here. Are you thinking there be an argument for both to have full cli control or do you think deployments alone would suffice?

# both deployments and modules could be treated as: "deployment IN deployments AND module IN modules"
runway (deploy|takeoff) --deployments (<name>|<index>),(<name>|<index>) --modules (<name>|<index>),(<name>|<index>)

# or just deployments
runway (deploy|takeoff) --deployments (<name>|<index>),(<name>|<index>)

allow optional tags to be specified on modules

This is an interesting idea for grouping. The same effect could be achieved through what I mentioned above. While I'm not opposed to adding tags, I think the --deployments and --modules options may be a more natural introduction. Thoughts?

[troyready]

When I was first typing out the issue I really intended to just mention modules (seemed more simple than trying to include deployments too), but then I just went and donked it up.

Upon further reflection, I'm more strongly convinced to just go for a per-module tag system. For most configs with a single deployment, the tag option will function as a module selector. And for more complex multi-deployment configs there will be enough flexibility to accommodate any selection.