configuration propagation

[phobologic]

The base groundwork is there for allowing for configuration propagation, but there's still a lot of work to be done. It'd be great if the scheduler pushed it's config + resources into an S3 bucket with a key name that matches the version hash for them. It should then include the version of the config that tasks are generated from - when a probe receives a task from a version it isn't running it could update itself from S3.

Same with the reactors - when they get a result from a config version they aren't running they should grab the new config from S3 and restart.

[phobologic]

An issue is that the config.yaml is loaded separately from the resources.yaml, which results in two different version hashes. Not sure what to do with that - combine them? Create a new hash of the hashes?

Definitely shouldn't pass nodes config along as that should change rather dynamically, and likely shouldn't matter to anyone but the scheduler.