Script to generate default `epinow2` task configurations

[amondal2]

Closes #3 --

This piece of the script handles generating the default set (i.e., all state-pathogen combinations) of task configurations. Future pieces will accept parameters (for now I've left them as parameters injected into the environment via os.environ, but this might change once I figure out how to integrate this with GHA) and generate only the specified tasks. Currently, this only handles one report_date.

I'll create issues separately for

• Integrating with GHA
• Test suite
• Pushing to blob storage

but wanted to make sure the actual generation piece looks correct. @zsusswein @natemcintosh I left some clarifying questions in the comments. Thanks!

[amondal2]

Thanks @natemcintosh for the suggestions! Will incorporate shortly

[zsusswein]

Got caught with Rt production stuff. Will try to look before I log off today

[amondal2]

Added type hints and using date type throughout. @natemcintosh

[amondal2]

Thanks @zsusswein -- I will address your in-line questions comments but to your main points

• I think what you said in #5 makes sense. This repo can handle scheduled generation and some default tasks, but the CLI will be able to handle modifying individual tasks in a more fine-grained way (modifying priors, state exclusions, etc)
• The task ID has the state/disease pair currently -- what were you thinking for a slug for the job id? Can update accordingly
• Config version would be good; I think we need to have a discussion later on about exclusions of tasks altogether. We could do something where we have by default an include=True for all tasks, and then the CLI could set that to False if we want to exclude a certain task later on. Open to ideas on this
• Will update pathogen -> disease

[zsusswein]

what were you thinking for a slug for the job id?

See here