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.

先檢閱 subprocess 模組文件和 issue 101283，接著比較 Popen、run()、call()、check_call() 與 check_output() 的 versionchanged 和 versionadded 註解。檢查這些 API 對 cwd、input、text、encoding 和 errors 的文件說明方式。完成的標準是這些註解遵循一致的策略，且沒有重複或互相衝突的描述。