Merged hgitaly2 branch into default branch
This long-running named branch was to carry intrusive changes necessary for operation without any auxiliary Git repository. As of !65, we've reached the point were everything is neatly separated and fully optional, depending on choices made by the other Heptapod components. I have checked as thoroughly as possible that using the `hgitaly2` branch of py-heptapod didn't break anything (unit/integration tests, functional tests).
!66 with topic/default/merge-hgitaly2 in 3 minutes and 30 seconds (queued for 3 seconds)5 jobs for