Add support for `etch` cheatcode (from Foundry)

[rappie]

https://book.getfoundry.sh/cheatcodes/etch
"Sets the bytecode of an address who to code."

This could be useful in multiple ways.

The main reason I'd like this is to be able to turn an EOA into a Contract to test how the target contract deals with this.

Another use is to debug/alter deployed contract onchain like this:
https://twitter.com/apoorvlathey/status/1621986610068996096

[gustavo-grieco]

is this really need with the deployBytecode option? 🤔

[rappie]

Does deployBytecode support overwriting code on onchain addresses?

[gustavo-grieco]

I don't know, this should be tested.

[GalloDaSballo]

I think ideally this cheatcode is added as it's the last one needed to make Echidna, Foundry and Medusa mostly compatible

[GalloDaSballo]

I was using this to fuzz something tied to Superfluid

And noticed a discrepancy between etch and deployBytecodes

Etch code:
https://github.com/superfluid-finance/protocol-monorepo/blob/dev/packages/ethereum-contracts/contracts/libs/ERC1820RegistryCompiled.sol

There's a prefix in deployBytecodes that is necessary (have tried pasting the etch bytecode to no success)
https://github.com/superfluid-finance/protocol-monorepo/blob/b86ec54fb628a8e28977d52c95b8aac0b1db20c3/packages/hot-fuzz/hot-fuzz#L67

[elopez]

@GalloDaSballo deployBytecodes takes the "contract creation code" you can find on e.g. Etherscan. This is executed on a transaction to create the contract instance in the VM.

https://etherscan.io/address/0x1820a4b7618bde71dce8cdc73aab6c95905fad24#code

It looks like etch may only take the final bytecode that got stored for the address ("deployed bytecode" on Etherscan) and thus does no execution/deployment? I suspect this may be limiting in some cases as the contract would not be able to do any initialization.