Inital attempt at an algorithm here. This involves working backwards commit by commit as it lets us know what resources to load in each commit, as we checkout each version. (without going back, or loading everything into memory each time)

1. use go-git library
2. we will re-use the existing code for handling watch events, which work on old/new resource objects
3. open the resource watch repo and checkout HEAD
4. load commit that is HEAD and see what file changed, it's only ever one, it might be add modify or delete.
5. deserialize that resources yaml, this is our "new" resource
6. load previous commit
7. deserialize same resource as next commit (if it was an update/modify), this is our "old" resource
8. call appropriate pre-existing watch handler from pkg/monitor/operator.go, pod.go, etc for our add/delete/update and new/old resource.
9. now lookup what file changed in this commit, and repeat the process
10. work all the way back to the first commit in the repo
11. we now have our source / raw intervals in reverse order