gh-153364: Add frame limit in get_async_stack_trace() and parse_coro_chain()

[maurycy]

Fixes #153364

The PR hardens and cleans up max frame chain limits a bit.

It introduces a const (MAX_FRAME_CHAIN_DEPTH), uses it in the existing process_frame_chain(), which is called by get_stack_trace(), as well as adds it to parse_coro_chain(), used in both sync and async pathways, and to parse_async_frame_chain().

The obvious context here is avoiding infinite loops. Truth be told, I think that in some places it unexpectedly works (ie: doesn't hang) because incomplete / torn-reads result in an exception. :-)

• Issue: _remote_debugging: No frame limit in get_async_stack_trace() #153364

[maurycy]

Does it actually need to be recursive?

To put aside recursive v. iterative; CS101 strikes: if you ask me, I was thinking about a visited set here... not applicable to this fix but cycle detected would be such a nice touch. :-)

[maurycy]

I realized we used Floyd's algo at least once:

cpython/Python/errors.c

Line 210 in 0c6422f

PyObject *slow_o = o; /* Floyd's cycle detection algo */

I, for one, like Brent's :-)

[maurycy]

Not the scope but maybe MAX_THREADS, MAX_STACK_CHUNKS, MAX_LINETABLE_ENTRIES or MAX_ITERATIONS are worth keeping here too