Config Files with Time Dependence

Recording this convo off slack because I'm not sure if I'm getting to it soon (open for others to take).

We've already hit one point in the automated data packaging where it would be nice to be able to have a configuration file where a number could be set for one range of time and then changed for another range of time. This is based off hardware changes during "operations" at UCSD. I expect we'll see more of these when we get onsite.

It's probably possible to build off this lookup_conditional function to build a short way of saving / loading time dependent from a config file. Having a standard easy way to do this would be nice.

(Somewhat related, it seems like ManifestDbs were almost built for this sort of thing by I'm not quite sure how it would work in this sort of instance. More thought there could also be an option. )

Start by reading the documented lookup_conditional function in sotodlib.site_pipeline.util and review how ManifestDbs might apply to automated data packaging. Define the expected configuration format and time-range behavior before choosing an approach. Done means a standard way to save and load time-dependent configuration values is agreed and implemented.