Eventual 2.0 release

[elijahbenizzy]

This is to track ideas for the eventual 2.0 release. Not going to do this for a while, but wanted to make sure we already have something around for later reference. So far I've got:

• Actually deprecate the old parameterization decorators
• Add a comprehensive subclass checker, make it separate, and ensure that its 100% correct (possibly release/use an OS version if possible).
• Pluggable (non-DFS) execution methods

[elijahbenizzy]

Some other ideas (not sure if before 2.0 or after):

1. Documentation generator
2. CLI

# Generates documentation
hamilton docs --format=sphinx --module=my_funcs --module=my_funcs_2 

# Runs it, materializing as intended
hamilton run --module=my_funcs --module=my_funcs_2 --mode=Dask --materialization=Foo --config=./config.json  # could have plugins here that represent drivers

# Provides a trace/explanation
hamilton trace --module=my_funcs --module=my_funcs_2 --input-vars=my_funcs --config=./config.json

[elijahbenizzy]

More general materialization -- not sure what the API should look like, but tags could easily allow for more structured materialization. Think dbt's view/table/ephemeral/incremental.