Apart from this being the "modern way" to do things, this would allow us to use dependency groups. Nowadays we have a hodgepodge of dependencies in requirements-tests.txt for various purposes. This not only install unnecessary installs, it can also make unrelated tests fail if there is a problem with a more exotic requirement.

That said, splitting the requirements into groups would be a second step (and issue).