Design scalable AIP arguments structure to support adding new features

[verovaleros]

We will continue adding new functionality and options to AIP (metrics, generate blocklists for range, comparisons, etc).

Would be great to have some sort of structure for argparse so we don't just keep adding arguments without thinking through the whole structure.

[verovaleros]

blocks #68

[verovaleros]

I think we can use subparsers for extra functionality. By default, it would run as it normally does from bin/aip running all models for today.

We could have a command bin/aip run which can support several scenarios:

• Run all models for a specific day
• Run a given model for a specific day.
• Run all models between two dates.
• Run a specific model between two dates.

[verovaleros]

Another command can be --rebuild-kb, which now takes a date. This could be bin/aip rebuild-kb which can take a date as input --start-date or something like that.

[verovaleros]

I think argparse should work for now, but in the future we may want to migrate to click or typer if it brings more flexibility.

[verovaleros]

The idea is then:

• Maintain current functionality
• Migrate --rebuild-kb to subparser command rebuild-knowledge-base
• Migrate --date and --model to subparser command run-models

[verovaleros]

It's very frustrating that for argparse the global arguments need to be called first, e.g.:

bin/aip -v rebuild-kb --start-date YYYY-MM-DD