CLI support base commit hash file as an input about target-determinator HOT 1 OPEN

Thanks for filing this issue! I think this makes a lot of sense - definitely being able to cache these values across runs is very sensible.

Would you be interested in trying to put together a PR to implement this? The key pieces of code to affect would be:

1. The entry-point here should optionally take a path to a hash file instead of a RevisionBefore - I'd probably introduce a new struct HashFileOrRevision which has either a HashFile or Revision set, and populate that on config.
2. This calls into WalkAffectedTargets - accept a HashFileOrRevision for commitishBefore and pass it through to FullyProcess.
3. In FullyProcess, populate queryInfoBefore by optionally deserializing JSON instead of calling fullyProcessRevision.

As far as I know, everything in QueryResults should be trivially JSON serializable (I think we'd need to add a Marshall implementation to MatchingTargets, but it's just a wrapper around a slice, so should be trivial).

We may want to nil-out any instances of analysis.ConfiguredTarget because they're probably very large and not useful other than for explaining why something changed. In fact, maybe all we want is to serialize MatchingTargets and TargetHashCache.cache, which maybe calls for its own struct purpose made for serialization/deserialization? We may also want to add some schema version number or similar but we can probably worry about that kind of thing in the future.

from target-determinator.