Consensus stops proposing blocks after committee rotation with majority of new nodes

[oleksandrSydorenkoJ]

Preconditions
Fair chain 4 committee nodes
7 active nodes total (4 commitee+3 observer)
Connected passive archive node

Versions
skalenetwork/schain:4.1.0-develop.56-fair

Steps to reproduce

1. Set rotation delay to 30 minutes
2. Run committee rotation with 3 new nodes in a committee (not participated in a previous group)
3. Wait for the transition delay

Expected state
Consensus should start mining blocks with a new group after the committee rotation

Actual state:
Consensus tries to create the first block after the transition delay with the previous node group instead of a new group.
amount of nodes

Logs:
1st committee rotation
NodeId 4 node was in both the previous and the actual groups
4-node-new-in-committee-4.1.0-develop.56-fair_committee-rotation-majority-of-nodes-in-group.txt

NodeId 1 node from the previous committee
4.1.0-develop.56-fair_committee-rotation-majority-of-nodes-in-group.txt