fix StuckInCatchup/Bootstrap alerts

[ghost-not-in-the-shell]

Explain your changes:
This PR fixes alerts StuckInCatchup and StuckInBootstrap

Explain how you tested your changes:
*

Checklist:

• Dependency versions are unchanged
  • Notify Velocity team if dependencies must change in CI
• Modified the current draft of release notes with details on what is completed or incomplete within this project
• Document code purpose, how to use it
  • Mention expected invariants, implicit constraints
• Tests were added for the new behavior
  • Document test purpose, significance of failures
  • Test names should reflect their purpose
• All tests pass (CI will check this if you didn't)
• Serialized types are in stable-versioned modules
• Does this close issues? List them

• Closes #0000

[ghost-not-in-the-shell]

!ci-build-me

[ghost-not-in-the-shell]

!ci-build-me

[ghost-not-in-the-shell]

!ci-build-me

[nholland94]

Just a note: I think this approach may trigger this alert if a node that was in bootstrap exits bootstrap and then re-enters bootstrap again, since the rate function in prometheus do not skip breaks in data, they only filter out drops in values. When you apply the syncStatus filter here, you are causing a break in the data, but when the data matches the filter again, there will be a massive observed jump in the process_update_ms_total between the breaks, which will still be observed in the final output of this query.

Let's merge this for now, as we need a new metric to fix this. Something like current_sync_status_process_uptime_ms_total which is a counter that resets every time syncStatus changes.