Support CREATE2 opcode

[tinker-michaelj]

EIP-1014 introduced the CREATE2 opcode to let a contract be deployed to a predictable address. Distributed exchanges, for example, make heavy use of the CREATE2 opcode. It can also be used to improve user onboarding flows.

On Hedera today, the Solidity address of a contract is derived from the contract's 0.0.X id, where X is a ledger-wide unique number that increments with each new entity created on the ledger. This address is 20 bytes where the first 12 bytes are all 0's and the last 8 bytes are the big-endian representation of X.

For example, the Solidity address of contract 0.0.1001 is

0x00000000000000000000000000000000000003e9

Furthermore, because each Hedera entity must have a unique 0.0.X id, there is no way to predict before a ContractCreate has been handled what the new contract's address will be. So there was no obvious way to implement CREATE2.

But after HIP-32, there is now a mechanism in the code that provides a level of indirection between a ByteString "alias" and a 0.0.X id. This idea is to implement CREATE2 by using the alias mechanism to link the deterministic address specified in EIP-1014 to the new contract's 0.0.X id.