Stderr in regular tests should probably go to out as well

[out] in regular tests should probably include stderr as well.

Recently, while making https://github.com/python/mypy/pull/19494, I learned that normal tests do not account for errors that go to stderr instead of stdout. This should be fixed, if possible (without performance penalty, so that normal tests can run a broader swath of tests.

This would allow more tests to be moved from slow cmdline tests to fast normal tests, à la https://github.com/python/mypy/issues/5966

I tried mucking about with the invocation of build.build in what struck me as the obvious ways, but even though I was able to get various ---------------------------- Captured stderr call ----------------------------- messages to pop off, I couldn't get the stderr to actually go into [out], even in a very crude way.

I'm not sure about how all this is plumbed, but it seems to me there's a minimal risk of erroneous stderr output messing up unrelated tests with false positives (or are they false negatives?), if we did have this working.

Commencez par suivre la manière dont les tests classiques invoquent build.build et la manière dont [out] capture actuellement la sortie, puis comparez ce chemin à celui des tests de ligne de commande lents référencés. Le travail est terminé lorsque stderr est inclus dans [out] pour les tests classiques sans pénalité de performances, ce qui permet de déplacer les tests appropriés vers le chemin plus rapide.