fix(consensus): valid/locked block incorrectly marked as not timely

[lklimek]

Issue being fixed or feature implemented

Due to invalid handling of ValidBlock/LockedBlock receive time, Tenderdash interprets some blocks as not timely.
It causes unnecessary PrepareProposal calls when previous block should be reused but is not due to "not timely" issue, as well as rejecting blocks as "not timely" during voting.

This can also trigger issues if ABCI App response prepare proposal changes between rounds.

What was done?

1. Fixed valid block and locked block update logic
2. Fixed "timely proposal" condition
3. Fire "valid block" event only when block really changed
4. Detect non-deterministic responses to PrepareProposal

How Has This Been Tested?

Github Actions + tested during Dash Platform load tests

Breaking Changes

None

Checklist:

• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have added or updated relevant unit/integration/functional/e2e tests
• I have made corresponding changes to the documentation

For repository code-owners and collaborators only

• I have assigned this pull request to a milestone

[shumkov]

👍