fix: handle service restarts

[MicaiahReid]

Description

Improves how we handle a restart of chainhook service while predicates are scanning/streaming. Here are the cases we now handle:

1. Predicates that were in scanning status when Chainhook was terminated will resume scanning starting from their last_evaluated_block_height. Note: because we only save predicate status every 10 scans, we could end up re-emiting matches on a resetart
2. Predicates that were in new status when Chainhook was terminated will start scanning at the predicate's start_block
3. Predicates that were in streaming status will return to a scanning status, starting at last_evaluated_block_height to catch up on the missed blocks. Note, the number_of_blocks_to_scan is set to 0 for this temporary catch-up, as it's difficult to compute the number of remaining blocks in the context of this change
4. If predicates were passed in at startup, we also register those to begin scanning, which previously didn't happen
5. We now allow passing in a predicate at startup and registering additional predicates with the predicate registration server. This means that if you use the same startup predicate repeatedly, it will already be saved in redis and not be reloaded.

Fixes: #298, fixes #390, fixes #402, fixes #403

---

Checklist

• All tests pass
• Tests added in this PR (if applicable)