refactor: update bloatnet benchmark cases

[LouisTsai-Csie]

Background

The fill command creates the full state by generating a genesis file containing all accounts and contracts. In contrast, the execute command connects to a client on given network and sends txs to deploy the required contracts and accounts.

For bloatnet, the state and contracts can be extremely large, making fill operation infeasible. In this case, using execute with stubs is a better approach (see docs). All required contracts in bloatnet can be deployed with a seed, and by reusing the same seed and stubbed contracts, the tests remain reproducible.

Description

Bloatnet-related tests were first introduced in PRs #2040 and #2090. While PR #2090 included a deployment script for the CREATE2 factory and other contracts. It would be better to split this functionality into a separate PR to follow the EEST framework.

The goal is to explore the existing framework and identify the best way to integrate deployment functionality, for example, by adding a specific CLI tool or extending the execute command. The current source script is here, and here

Proposed Solution

1. Add a new deploy_create2_targets method for pre_alloc

cc @jochem-brouwer @CPerezz