fix: determine F3 participants relative to current network name

[masih]

Related Issues

Fixes #12519

Proposed Changes

When manifest changes, depending on the timing it is possible for newly generated valid leases to get removed if the sign message loop attempts to sign messages that are as a result of progressing previous network.

Here is an example scenario in a specific order that was causing itests to fail:

• participants get a lease for network A up to instance 5
• network A progresses to instance 6
• manifest changes the network name to B
• participants get a new lease for network B up to instance 5
• sign loop receives a message from network A, instance 6
• getParticipantsByInstance lazily removes leases since it only
  checks the instance.
• the node ends up with no participants, and stuck.

To fix this:

1. check if participants asked for are within the current network, and if not refuse to participate.
2. check network name, as well as instance, to lazily remove expired leases.

To aid debugging failing tests in the future add option to print progress of all nodes at every eventual assertion, disabled by default.

Additional Info

Look closely at the commits in this PR. The commits introduce a dedicated CI job that repeatedly runs the flaky tests (50 times) to assert that they are indeed fixed. The job is then removed in later commits.

These commits are left here for the benefit of the reviewer as proof of the pudding.

Checklist

Before you mark the PR ready for review, please make sure that:

• Commits have a clear commit message.
• PR title conforms with contribution conventions
• Update CHANGELOG.md or signal that this change does not need it per contribution conventions
• New features have usage guidelines and / or documentation updates in
  • Lotus Documentation
  • Discussion Tutorials
• Tests exist for new functionality or change in behavior
• CI is green