fix: priority problem

[zsystm]

problem

• calculation priority is non-deterministic
  • e.g., multiple rounds for future heights and catch up
• priority is not handled consensus state (no validation for this value, check how Validator set's hash is calculated)

solution

• (short-term) reset priorities
• (long-term) treat priority as consensus state

[dudong2]

Node Operation and Resynchronization Test Scenario

1. Nodes 1, 2, 3, and 4 are started and running normally.
2. Nodes 1, 2, and 3 are stopped at block height 10 and then restarted with --reset-priority-height 10. This causes node 4 to proceed with a different priority state compared to the other nodes, leading to continuous invalid proposal signature errors due to the proposer being different from the expected one.
3. The blockchain proceeds until block 20.
4. All four nodes (1, 2, 3, and 4) are then stopped and restarted with --reset-priority-height 20.
5. Finally, verify if the nodes synchronize correctly after the restart.