[signer] A signer should no longer view a miner as invalid due to inactivity if a majority of signers approve its blocks

[jferrant]

This is more of a question than an actual request.

This is the current flow:
Suppose we have Signers 1 through N.
Signer 1 sets block_proposal_timeout to x seconds.
x seconds pass for Signer 1.
Miner A issues a block proposal N.
SIgner 1 marks miner B as invalid and refuses to sign its block.
Signer 2 through N, receive block proposal N before their own block_proposal_timeouts.
Block N is signed and broadcasted.
Miner A issues block proposal N+1.
Signer 1 still views Miner A as invalid and rejects the block.
Signers 2 through N approve N+1.

My question is, should Signer 1 recognize that Miner A is viewed as valid by a majority of the network and decide to start signing its blocks again? I don't think a miner marked invalid should always become valid again if it produces blocks, but I am wondering if the reason it was marked invalid is due to the block_proposal_timeout, maybe in this case if its production succeeds anyway, the signer should mark it valid and sign subsequent blocks.

Open to suggestions as this does complicate the network a bit.