[davepacheco]

Fixes #5010.

This adds a new top-level blueprint field called ReflectsCollection that's an enum that either describes a specific inventory collection (with its id, time started, and time done) or else Indeterminate. The expectation is that planner-created blueprints would always supply information about the collection that the planner used. But other blueprints (the RSS ones, test ones, reconfigurator-cli edits, and ones already in the database that get migrated to this change). I opted to require that callers of BlueprintBuilder::new_based_on specify this because I felt a default was too easy to get wrong. But that's why this PR touches so many files -- to fix up a ton of test callers.

For now, this is only for debugging. This information could be used to implement an autoplanner heuristic like: don't run the planner if the collection you have is older than the one in the current target blueprint. I considered putting this information in the planning report instead (which means we could skip all the db code here), but that would make it unusable for this purpose since the planning report is not programmatically accessible to Nexus.

[davepacheco]

I'm torn about the approach to Diesel here. I would not have produced this code. But it does have the property that consumers are not exposed to the fact that there are three underlying fields here, and you cannot have an in-memory representation that's not valid (a mix of None and non-None values). I'm open to doing this a different way though.