Implement State Bloating scenarios for Bloatnet

[CPerezz]

https://bloatnet.info/ initiative attempts to clear the doubts on when state-size will become an issue for clients and which will be the exact triggers that will require work.

This initiative, requires 2 things: Bloating scenarios & attack scenarios.

Bloating Scenarios

These refer to all the scenarios whose goal is to increate state size as much as possible with a single tx.

• Deploy max contracts in a single block adapted to gas_limit ((feat) Introduce contract-deployment bloating scenario #41 )
• Set maximum amount of authorisations in a single block to already funded EOAs (feat(eao-delegation): Create eoa-delegation scenario oriented to state-bloating #68 )
• Set maximum amount of contract storage in random positions in a single block (feat(rand_sstore_bloater): add SSTOREStorageBloater contract and scenario #69 )
• Create the maximum amount of new accounts by funding them with 1token bloating contract storage (feat: Introduce erc20_max_transfers scenario for bloating #70 )

Notice some of these scenarios will serve as attacks too when testing at 100M gas-limit.

Attack Scenarios

• Perform the maximum amount of EXTCODESIZE to 24kB contracts in a single block.
• Perform the maximum amount of SLOADs to random slots introduced by rand_sstore scenario
• Implement XEN contract worst-cases adaptative to max gas-limit
• Perform max amount of warm EXTCODESIZE by calling BALANCE first for all of them. This exploits the warm access discount and exploits a double-access to the same contract in a possibly lost-cache entry.