fix(tests): incorrect max_stack_height issues

[marioevz]

I believe this change solves the max-stack-height issues by doing this trick at the start of each section creation:

code = Bytecode(min_stack_height=inputs, max_stack_height=inputs)

So now the stack operations that are performed during the construction of the code section take the input stack height as the starting point.

We are now left with three different kinds of exceptions in the remaining failing tests (when no_expectations_on_validity is not used):

• EOFException.STACK_HEIGHT_MISMATCH
• EOFException.STACK_HIGHER_THAN_OUTPUTS
• EOFException.STACK_UNDERFLOW

[pdobacz]

Oh, that would be great, so simple. Let me delve in and see how this impacts the codes.

[pdobacz]

Hey, I incorporated your commit in my branch, along with some other commits, and pushed, and GH figured it out as merged 🎉 . Thank you again.