Load config history

[JosephMarinier]

Description:

• Make config path optional, defaulting to loading config from env vars only, for example:

make ARTIFACT_PATH=cache REJECTION_CLASS=NO_INTENT DATASET='{
    "class_name": "loading_resources.load_CLINC150_data",
    "remote": "'$PWD'/azimuth_shr",
    "kwargs": {
        "python_loader": "'$PWD'/azimuth_shr/data/CLINC150.py",
        "full_path": "'$PWD'/azimuth_shr/files/clinc-demo/oos-eval/data/clinc_data_dummy.json"
    }
}' launch.local

• Support launching Azimuth from config history
• Change artifact_path default to "cache"
• Make dataset config optional, relying on our (already existing) code to validate that the dataset is defined after loading the final config.

Checklist:

You should check all boxes before the PR is ready. If a box does not apply, check it to acknowledge it.

• ISSUE NUMBER. You linked the issue number (Ex: Resolve #XXX).
• PRE-COMMIT. You ran pre-commit on all commits, or else, you
  ran pre-commit run --all-files at the end.
• USER CHANGES. The changes are added to CHANGELOG.md and the documentation, if they impact
  our users.
• DEV CHANGES.
  • Update the documentation if this PR changes how to develop/launch on the app.
  • Update the README files and our wiki for any big design decisions, if relevant.
  • Add unit tests, docstrings, typing and comments for complex sections.

[gabegma]

Thank you for taking the time to make a clear PR. I was hesitant, but I see it more clearly now. I like it. So the default is to ignore the history, right? So no confusion if someone does make CFG_PATH='bla.json' launch; they will see 'bla' in Azimuth, no matter the config history.

[JosephMarinier]

In our Python code, we could consider making "cache" the default artifact path, useful locally, rather than "/cache", useful in docker, and set it to "/cache" in our Dockerfile. Tha would simplify:

Suggested change

	make ARTIFACT_PATH=cache LOAD_CONFIG_HISTORY=1 launch.local
	make LOAD_CONFIG_HISTORY=1 launch.local

[gabegma]

Yeah, looks like a good idea

[JosephMarinier]

Done in bf8861a

I like it. It also makes the documentation more straightforward; a simpler description of the "normal" use case with the default artifact_path, and then a warning box about customizing artifact_path.

[gabegma]

LGTM!! Awesome new feature, great work!