gh-96894: Do not turn echo off for subsequent commands in batch activators

[pawelszramowski]

Some @ are certainly unnecessary but I don't feel confident enough to optimize.

Closes #96894

• Issue: Batch activators unexpectedly turn echo off for subsequent commands #96894

[ghost]

All commit authors signed the Contributor License Agreement.

[vsajip]

This seems a bit brittle (e.g. if new lines are added) - can't the echo be turned off and then back on at exit points, rather than almost every line being changed?

[pawelszramowski]

Unfortunately, there's no reasonable way to restore the caller's setting when you're done (yeah, batch is crap):

• https://stackoverflow.com/questions/9592732/restore-the-previous-echo-status
• https://stackoverflow.com/questions/48420074/was-echo-on-or-off-when-my-windows-bat-was-called

[pawelszramowski]

@vsajip ping :)

[arhadthedev]

@python/windows-team

[pawelszramowski]

@vsajip ping again! Please approve, assign a different reviewer, or let me know what you would like me to change.

[zooba]

Looks fine to me. Leaving for @vsajip to merge/object

[python-cla-bot]

All commit authors signed the Contributor License Agreement.

[github-actions]

This PR is stale because it has been open for 30 days with no activity.

[zooba]

Better late than never.