EVM/Sequencer: limit the size of blueprints

What

Adds a limit in the number of chunks per blueprints.

TODO:

• Add tests

Why

According to the tick model and recent benchmarks, the size of blueprints can be problematic, it takes too much ticks and takes too much L1 levels to send the chunks. As L1 blocks are limited to 512KB, it doesn't make sense to create bleupritns bigger than that as it would make the rollup lag behind the sequencer.

How

• Enforce pop_transactions to limit the number of transactions removed from the pool
• Count the size of delayed transactions as part of the complete blueprint

Manually testing the MR

Checklist

• Document the interface of any function added or modified (see the coding guidelines)
• Document any change to the user interface, including configuration parameters (see node configuration)
• Provide automatic testing (see the testing guide).
• For new features and bug fixes, add an item in the appropriate changelog (docs/protocols/alpha.rst for the protocol and the environment, CHANGES.rst at the root of the repository for everything else).
• Select suitable reviewers using the Reviewers field below.
• Select as Assignee the next person who should take action on that MR