subprocess module docs contain an inconsistent mix of repeated versionchanged descriptions

Documentation

The subprocess module documentation has an explosion of repeated text in versionchanged or versionadded markers splattered over multiple APIs within the docs.

The reality is that many of these are technically all directly Popen API changes, that the other higher level preferred more user friendly APIs like run() and call() and check_call() and check_output() all make use of internally and forward a majority of their arguments to.

Examples to look for: where are cwd, input, text, encoding, errors argument behavior changes/additions mentioned vs which APIs accept these.

I noticed this when looking over the changes made in https://github.com/python/cpython/issues/101283 where it became apparent to me that we're not internally consistent in how we do this within the doc today. The doc needs some cleanup and a strategy for this.

Comece revisando a documentação do módulo subprocess e a issue 101283; em seguida, compare as notas versionchanged e versionadded para Popen, run(), call(), check_call() e check_output(). Verifique como cwd, input, text, encoding e errors são documentados nessas APIs. Considera-se concluído quando as notas seguem uma estratégia consistente, sem descrições repetidas ou conflitantes.