node: Re-enable consensus task on a failed block acceptance

[goshawk-3]

Summary

If a block is distributed with a valid certificate but contains erroneous transactions, the node should reject the block and reactivate the consensus process for the corresponding round. Presently, we reject these blocks; however, the consensus procedure remains inactive.

[fed-franz]

Does this refer to the synchronization process or do we have other situations in which we stop consensus?

BTW, an invalid block with a valid certificate would be quite worrisome...it would most likely mean the network is corrupted.

[herr-seppia]

This has been solved with https://github.com/dusk-network/rusk/pull/1831/commits/29e3d6b020bf3b7ce1aff2cc819bad1996d17532