fix: correct error message for stdout pipe check in run_process

[nightcityblade]

Fixes #3409

The error message for the stdout=subprocess.PIPE check in run_process incorrectly said "stdin=subprocess.PIPE". This fixes it to say "stdout=subprocess.PIPE".

This is a recreation of #3398 with the same fix plus a newsfragment.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00000%. Comparing base (3dd35d7) to head (97ba75c).
⚠️ Report is 14 commits behind head on main.

Additional details and impacted files

@@               Coverage Diff               @@
##                 main        #3416   +/-   ##
===============================================
  Coverage   100.00000%   100.00000%           
===============================================
  Files             128          128           
  Lines           19424        19417    -7     
  Branches         1318         1318           
===============================================
- Hits            19424        19417    -7     

Files with missing lines	Coverage Δ
src/trio/_subprocess.py	100.00000% <ø> (ø)
src/trio/_tests/test_subprocess.py	100.00000% <100.00000%> (ø)

... and 8 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[CoolCat467]

You forgot to update the tests mate

[nightcityblade]

Good catch @CoolCat467! Updated the test to match the corrected error message — the stdin pipe check now expects stdin=subprocess.PIPE instead of stdout=subprocess.PIPE. Thanks for the review!

[A5rocks]

Please fix the news fragment syntax!

[A5rocks]

The last part uses a * but I think the regex can be more specific.

(Same comment applies for the one above, too)

[nightcityblade]

Fixed — switched to double backticks (code) for proper RST syntax. Thanks @A5rocks!

[A5rocks]

Please address the review too! (and you don't need to write out a comment acknowledging what you finished; the commits have that data.)

[A5rocks]

Sorry, I was thinking something like this. What do you think?

[A5rocks]

Suggested change

	pipe_stdin_error = r"^stdin=subprocess\.PIPE is only valid with nursery\.start, since that's the only way to access the pipe(; use nursery\.start or pass the data you want to write directly)?$"
	pipe_stdin_error = r"^stdin=subprocess\.PIPE is only valid with nursery\.start, since that's the only way to access the pipe; use nursery\.start or pass the data you want to write directly$"

[A5rocks]

Suggested change

	pipe_stdout_error = r"^stdout=subprocess\.PIPE is only valid with nursery\.start, since that's the only way to access the pipe(; use nursery\.start or pass the data you want to write directly)?$"
	pipe_stdout_error = r"^stdout=subprocess\.PIPE is only valid with nursery\.start, since that's the only way to access the pipe$"