engine/statusmgr: Skip status updates without an associated log entry

[mastercactapus]

Description:
This PR introduces logic to "skip" status updates that are missing log entries.

Currently, these updates will result in all status updates failing indefinitely, or until the alert has no changes for 7 days.

The new behavior has the following properties:

• If a log entry is missing for any reason, an error is logged, the status update is skipped, and the status subscription is updated. This means future updates will still be attempted.
• Since only log entries from the last hour are considered, that means 1 hour is the max possible delay for a status update (currently, it is indefinite)
• An "omit" list is kept during each engine cycle, ensuring each subscription is attempted at most once per engine cycle. If a status update fails today, it will be retried 100 times, blocking all others.

Which issue(s) this PR fixes:
Closes #3783

Additional Info:

• As per testing this, a dev bug was fixed where CTRL+C would fail to cancel unit tests or smoke tests.