verify-bytecode: support arbitrary contract creation methods

[adhusson]

Component

Forge

Describe the feature you would like

forge supports verify-bytecode on:

• predeploys
• contracts deployed by the EOA by setting tx.to = ''
• contracts deployed by setting tx.to = DEFAULT_CREATE2_DEPLOYER

In other cases it cannot find the contract creation code.

It would be useful to support arbitrarily nested calls to create and create2. For instance it would allow using a custom create2 deployer and still verifying with verify-bytecode.

I think this is achievable by stepping through the transaction and finding uses of CREATE/CREATE2 that return the created contract address, then reading the relevant memory segment when the opcode was used.

Additional context

No response