This might be a problem. We want a single source of truth for the enabled flag, which is the JobState class.  the enabled from the config is only relevant when a job is added, so that users can add a job without scheduling an initial run.  Once a job has state the config.enabled is ignored.

You should be able to remove this property by taking the following steps:
* move `schedude()` up into the `JobContainer`
* have `run_job()` accept an enabled flag
* move the top level state restore into the `JobContainer`, which will call a `restore_state()` on both the `JobState` and `JobScheduler`

This should work for now, and we can examine how to clean up run_job() further later.