Add gov proposal to update EVM smart contract

[omritoptix]

The idea is that we want gov controlled smart contract.
This can let developers integrate the power of the applicative logic with the gov logic and not being trapped within the multi-sig or immutability trade-off.

[omritoptix]

Quoting @VictorTrustyDev

Step 1: Prepare deployed bytecode (the new sausage).
Developer update contract code
Developer deploy the new contract code into testnet/mainnet/whatever, for 2 purpose: 1, for testing and 2, to get the deployed bytecode (the sausage). I'd suggest to deploy and test on mainnet because EVM SC has something called static library which referenced by address so different environment might results different address. Every referenced contract address must be taken care of very carefully.
At this point, you have the deployed bytecode (the sausage).
Step 2: Replace the deployed bytecode of an existing EVM smart contract.
In this step, you can design a new gov proposal handler to put deployed bytecode (the sausage) into x/evm store and reference the contract to the new key which stored the new deployed bytecode (new sausage).
So how to correctly replace existing deployed bytecode (old sausage) by the new deployed bycode (new sausage):
In x/evm store, the deployed bytecode fully saved in store and the store key is the code hash, which is computed from the deployed bytecode:
https://github.com/dymensionxyz/evmos/blob/v12.1.6/x/evm/keeper/statedb.go#L175
Then the contract referenced to the deployed bytecode by putting the code hash into the proto account.
https://github.com/dymensionxyz/evmos/blob/v12.1.6/proto/ethermint/types/v1/account.proto#L24
So to replace, yes you need to save deployed bytecode, referenced by it's code hash, and save the new code hash to proto account of the contract.
No EVM invocation is necessary.
EVM when need to read deployed bytecode for execution or smt, it will get the account, which contains the code hash, then get the deployed bytecode from the code hash.
That is why we replace it like above.
VERY IMPORTANT thing about smart contract data.
Due to data storage designed by EVM, similar to upgrade-able contracts, everything about the source code need to be taken care of, like order of variables.
Because EVM stores data by slot so changing order of variables will corrupt data.