revert in CREATE in init code, followed by returndatasize/copy

[pirapira]

Implements https://docs.google.com/spreadsheets/d/1xat7UI8GtB4ZGVdlK5_XQSHJZaMThi4SrlcL8XMZb5Q/edit#gid=1605675414&range=C59

[veox]

For ref: py-evm had a hiccup on this one.

Here's what I think is going on it the test: ethereum/py-evm#1224 (comment).

From gitter chat, the test rationale might be focusing on pre-Byzantium execution, not Byzantium itself:

maybe [Yoichi] was afraid that returndatasize might be 0 and so this way he checks that transaction fails on <Byzantium .

The "weird" part about the test is having a {zero-balance, no-code, zero-nonce, some-storage} account in the pre section:

tests/BlockchainTests/GeneralStateTests/stRevertTest/RevertInCreateInInit_d0g0v0.json

Lines 94 to 102 in 298749a

	"pre" : {
	"0x6295ee1b4f6dd65047762f924ecd367c17eabf8f" : {
	"balance" : "0x00",
	"code" : "",
	"nonce" : "0x00",
	"storage" : {
	"0x00" : "0x01"
	}
	},

The call to REVERT fails on pre-Byzantium, but is expected to have the storage filled on Byzantium:

tests/BlockchainTests/GeneralStateTests/stRevertTest/RevertInCreateInInit_d0g0v0.json

Lines 77 to 85 in 298749a

	"0x6295ee1b4f6dd65047762f924ecd367c17eabf8f" : {
	"balance" : "0x00",
	"code" : "",
	"nonce" : "0x02",
	"storage" : {
	"0x00" : "0x20",
	"0x01" : "0x112233"
	}
	},

The difference between py-evm and the test-as-specified is in gas use, and is discussed in more detail in the py-evm PR (first link of this comment).