Blocking command port when node is not caught up

[danieldoglas]

Details

This PR blocks the command port if a node is more than 12.5K commits behind the leader, and reopens when we're 1K behind.

Fixed Issues

Fixes https://github.com/Expensify/Expensify/issues/437855

Tests

---

Internal Testing Reminder: when changing bedrock, please compile auth against your new changes

[cead22]

Since we block the command port for other reasons, we should put the fact that this is being set based on the node being behind on the variable name, for clarity

Suggested change

	bool _blockedCommandPort{false};
	bool _blockedCommandPortForBeingBehind{false};

But do we really need this variable? Is there an easy way to check the reason the command port is blocked so we can do something like

_blockedCommandPortForBeingBehind = getReason() == "COMMITS_LAGGING_BEHIND";
if (peer == _leadPeer && currentCommitDifference >= 12'500 && !_blockedCommandPort) {
    ...

[danieldoglas]

But do we really need this variable? Is there an easy way to check the reason the command port is blocked so we can do something like

tl;dr: Adding this as a separate variable so we don't need to add complexity to the current methods related to block reasons. We had an implementation like you're suggesting before, but that would require adding new locks/changing current lock types.

This was discussed in this thread: https://expensify.slack.com/archives/CC7NECV4L/p1734981555759429?thread_ts=1733270912.693829&cid=CC7NECV4L