Make managing task variants / subversions easier

[haileyschoelkopf]

We now need to handle support for many many tasks, because tasks can have many slight variations that all need tracking.

We should see if there is a way to easily handle these (e.g. different prompts / prompting style archetypes, different translations, etc.) s.t. we do not need to have each of those being a separate task--possibly some sort of tagging system or way to parameterize tasks? A way to define tasks as config stubs which can take a list of predefined mixin configs?

Would need consideration but this is an important problem to solve for future maintainability and configuration.