tests: 🖋️ mock consensus engine can test validator uptime measurements

[cratelyn]

stub issue, see #3588. see #3995.

currently, the consensus keys in the keyring are not used by either the test node or block builder to sign blocks. we should introduce the ability to sign blocks, in order to test e.g. the staking component.

see section 8a in #3995. we will likely need to do some requirements discovery as part of that work, which should drive the fix to this issue.

• tests(app): 🎤 uptime tracker tests for validators missing blocks #4061
• tests(app): 🧪 test that uptime tracks signed blocks #4070
• refactor(staking): 🌹 hoist uptime tracking into ValidatorUptimeTracker extension trait #4099

[erwanor]

One thing to note is that the application doesn't actually verify signatures on blocks, it takes it as granted from the consensus layer (same for byzantine misbehavior evidence) so as long as mock consensus produces legible commit information (containing VoteInfos) the application will be able to track the uptime accurately.

[cratelyn]

One thing to note is that the application doesn't actually verify signatures on blocks, it takes it as granted from the consensus layer (same for byzantine misbehavior evidence) so as long as mock consensus produces legible commit information (containing VoteInfos) the application will be able to track the uptime accurately.

this is very helpful to know, thank you!