_remote_debugging.RemoteUnwinder.get_async_stack_trace() walks the target
process's asyncio awaited_by graph with an unbounded three-function C recursion
(process_task_and_waiters → process_task_awaited_by → process_waiter_task →
process_task_and_waiters, in Modules/_remote_debugging/asyncio.c). Each level
also stack-allocates char task_obj[SIZEOF_TASK_OBJ] (4096 bytes), so a deep or
cyclic graph in the target overflows the debugger's C stack and crashes it with
SIGSEGV. This is asymmetric with the iterative sibling path
(append_awaited_by_for_thread), which already bounds its walk with
MAX_ITERATIONS.

This PR bounds the recursion with an explicit depth cap
(MAX_TASK_AWAITED_BY_DEPTH, defined next to the existing MAX_ITERATIONS /
MAX_SET_TABLE_SIZE / MAX_* constants in _remote_debugging.h). The depth is
threaded through the existing generic processor/context callback via a small
waiter_context_t { result, depth }, so the public process_task_and_waiters
signature is unchanged (it stays a depth == 0 wrapper over the new
process_task_and_waiters_impl). On overflow the code raises a RuntimeError
through the module's existing set_exception_cause error path, matching how the
module reports every other "corrupted remote memory" condition. A depth counter
(rather than a visited-set) also covers a cyclic awaited_by graph from corrupted
remote memory, since each recursion still increments the depth.

The module already documents that the target's memory is untrusted input
(debug_offsets_validation.h), so a debugger reading an attacker-controlled or
merely deeply-nested target must not be crashable by the target's graph shape;
bounding this traversal is consistent with the module's existing invariants.

Adds test_async_deep_awaited_by_chain_is_bounded to
Lib/test/test_external_inspection.py: it spawns a target with a deep linear
awaited_by chain whose leaf is the running task and asserts that
get_async_stack_trace() raises RuntimeError ("too deep or cyclic") instead of
crashing.

Verified that the pre-fix interpreter segfaults (SIGSEGV) on a deep chain while the
patched interpreter raises a clean RuntimeError, and that a shallow chain still
returns a stack trace normally (negative control). The existing asyncio
stack-trace tests continue to pass.

Closes #151535

This change was prepared with AI assistance; I have reviewed and verified the code,
the reasoning, and the test myself.

• Issue: RemoteUnwinder.get_async_stack_trace() crashes with a C stack overflow on a deeply nested awaited_by graph instead of raising #151535