EVM/Kernel: refuse blueprints from the past

It's a long low hanging fruit. This merge request refuses sequencer blueprint chunks if they don't help making the chain progress. The current implementation is not problematic, but dealing with these blueprints is just not necessary.

I added a test that's a bit ugly but it tests what we want. It's on a higher level to make sure the code uses the current_number to check the validity, the test would have been simpler if I was testing at the parsing level, but less complete. I also added the test on the parsing level to be exhaustive.

The logs of the test are the following:

[Debug] Storing chunk 0 of sequencer blueprint number 7
[Debug] Sequencer blueprint refused because: SequencerBlueprint(InvalidSignature)
[Debug] Sequencer blueprint refused because: SequencerBlueprint(InvalidNumber)
[Debug] Sequencer blueprint refused because: SequencerBlueprint(InvalidNumber)