Strongly type dftimewolf input parameters

[ramo-j]

From OOB discussion:

dfTimewolf takes a lot of different input parameters (defined in recipes), but they're often the same
"type": dates, ticket IDs, etc. It's always up to the recipe / module writer to parse, validate, and
convert these into the appropriate datatype (e.g. dates), which creates a lot of repetition and opens
the codebase to more bugs.

It would be good to define an ontology of acceptable parameters and how to parse them and
migrate the existing ones.