Evaluation stack bounds are not checked in debug builds.

[markshannon]

Bug report

Bug description:

Prior to the generating code for the interpreter(s), we had a set of macros for stack manipulation, PUSH, POP, etc.
The code generator does not use these any more, which improves readability, but we have lost the runtime checking of bounds.
Having those bounds checks would have identified the issue with #120793 almost immediately.

We should add bounds checking asserts in the generated code.
E.g.
stack_pointer +=1 should be

stack_pointer += 1;
assert(WITH_STACK_BOUNDS(stack_pointer));

This bulks out the generated code a bit, but I think making the limit checks explicit is more readable than using stack adjustment macros.

CPython versions tested on:

CPython main branch

Operating systems tested on:

No response

Linked PRs

• GH-120982: Add stack check assertions to generated interpreter code #120992