Cannot verify with creation match contracts with onchain auxdata length different than compiled auxdata length #2645
Description
I discovered creation matches are not supported with the fix implemented in #2619 because in the creation bytecode exists a byte defining the length of the runtime bytecode after the creation section. If the bytecode length changes (bytecodeHash = none or appendCbor = none) then also that byte changes, and so a match is not possible. We could potentially support it in the future with an new transformation type
6080604052348015600f57600080fd5b5061 0127 (h0127=590 digits; length of the runtime bytecode) 8061001f6000396000f3fe (runtime bytecode starts (length 590) -> ) 608060405234801561001057600080fd5b50600436106100365760003560e01c80632e64cec11461003b5780636057361d14610059575b600080fd5b610043610075565b60405161005091906100a1565b60405180910390f35b610073600480360381019061006e91906100ed565b61007e565b005b60008054905090565b8060008190555050565b6000819050919050565b61009b81610088565b82525050565b60006020820190506100b66000830184610092565b92915050565b600080fd5b6100ca81610088565b81146100d557600080fd5b50565b6000813590506100e7816100c1565b92915050565b600060208284031215610103576101026100bc565b5b6000610111848285016100d8565b9150509291505056fea164736f6c634300081c000a