heptapod-paas-runner: persistent tracking of jobs

Currently, if heptapod-paas-runner is restarted, the new process won't know about jobs being tracked, and will hence

• not launch those that were acquired before restart (jobs will be hanging forever, from the coordinator point of view)
• not know about those already launched, hence can vastly outrun the maximal concurrency