Fix two flaky tests: slow-teardown timing and pdb EOF race

[RonnyPfannschmidt]

Requested by Ronny · project thread

🤖 Written by Claude Opus 5.5 via Claude Code for the pytest maintainers; I prompted it, it did the work, I read it.

Before: two tests fail intermittently in CI.

• TestTerminal::test_console_output_style_times_slow_teardown_does_not_leak (added in Bugfix 14412 subtests timing #14670) asserted that test_a2 shows a duration under 0.1s. On build (windows-py311) for Derive ExceptionInfo strip text lazily from the exception #15149 it failed twice on the same commit, with 0.2548 and 0.1947.
• TestPDB::test_pdb_and_capsys hit a pexpect timeout on build (ubuntu-py310-xdist) on this PR.

After: both tests are stable.

How

• Timing test: the assertion is now < 0.3. The test guards against test_a1's 300 ms teardown leaking into test_a2's reported time, and such a leak adds at least 0.3s. The measured 0.19–0.25s values are test_a2's own runtime on a slow runner, so < 0.3 still catches the leak without depending on runner speed.
• pdb test: it sent EOF right after seeing the readouterr() output, while pdb could still be processing the command, and the EOF was sometimes lost. It now waits for the next (Pdb) prompt first, like the other tests in test_debugging.py. Locally, under xdist with 16 workers, the test failed 7 of 600 runs before and 0 of 450 after.

Test-only changes, no changelog entry.

• Allow maintainers to push and squash when merging my commits.
• If AI agents were used, they are credited in Co-authored-by commit trailers.

🤖 Generated with Claude Code

https://claude.ai/code/session_01RPVUqQy85BXtPFPctRc71n

[RonnyPfannschmidt]

🤖 Written by Claude Opus 5.5 via Claude Code for the pytest maintainers; I prompted it, it did the work, I read it.

build (ubuntu-py310-xdist) failed in TestPDB::test_pdb_and_capsys with a pexpect timeout. It's a real race in the test: EOF was sent before pdb showed its next prompt. I reproduced it locally (7 failures in 600 runs) and fixed it in this PR (0 failures in 450 runs); see the updated description.