tool: compaction log tool should be DB re-open aware

Consider the case where a `JOB` is printed in the logs with a relatively low job ID. If the the DB is restarted, the job ID counter is reset, which can result in IDs repeating themselves in the logs. This can throw off the tool, for example, by thinking that a compaction took longer than it really did.

Ideally, the tool would be "re-open aware", and would not attempt to combine jobs from either side of the boundary.

Jira issue: PEBBLE-93