Proper treatment of YUL's `invalid()` in resolc/PVM

[TorstenStueber]

The semantics of YUL's invalid() is the semantics of the INVALID opcode, which reverts the current call and consumes all available gas.

This works correctly when compiling to EVM and executing with our EVM backend. But it does not work with resolc/PVM.

Expected Behavior

When compiling to PVM via resolc, then contract should end up calling the consume_all_gas host function. This function will ensure that all available gas in this frame is consumed.

Actual Behavior

When compiling to PVM and executing on pallet-revive, not all available gas is consumed.

Additional Bonus

This will allow us to un-ignore the call_invalid_opcode test. These tests work correctly in the cases "solc->solc" and resolc->solc" but not in the cases "solc->resolc" or "resolc->resolc".

[pgherveou]

I believe that this works now the test can be un-ignored
The test just seems to be buggy now
it passes u64::MAX to the child, so of course the whole call stack fails with an error, it should be refactored, passed less gas.
Might be worth to use the call traces here as well to ensure that indeed the gas passesd has been fully consumed

[0xRVE]

I left a TODO at this test as a reminder for us to decide how to handle that particular case:

// This test has a `caller` contract calling into a `callee` contract which then executes the
// INVALID opcode. INVALID consumes all gas which means that it will error with OutOfGas.

We can either make the test assert OutOfGas or we need to change implementation so that the Invalid error propagates from child to parent contract.

[xermicus]

I don't think it needs to be too complicated. Can just pass a very large gas stipend to a program that does nothing but hitting invalid and assert that it used all the gas.