Fix Interpreter discovery bug wrt. Microsoft Store shortcut using Latin-1

[rahuldevikar]

When virtualenv performs interpreter discovery on Windows, it spawns a subprocess to run the py_info.py script for each discovered Python interpreter. On systems where the Microsoft Store Python shortcut exists (but Python wasn't installed via MS Store), invoking this shortcut returns an error message in CP1252 encoding. On systems with non-English locales (e.g., German), these error messages contain characters like umlauts (ü) that can't be decoded as UTF-8, causing UnicodeDecodeError exceptions to appear in the terminal.

Use Latin-1 instead

update:
Forcing subprocess to use utf-8 mode

[rahuldevikar]

All tests are succeeding here: https://github.com/rahuldevikar/virtualenv/actions/runs/20727523037
Note, for some reason, the pipeline is using tox 1.1(and failing) and I have to hard push to use >= 4.32 as shown in the check.yml. It seems that the original repo is fetching the tox >= 4.32 somehow. I think the changes to check.yml should be safe enough but I need feedback on how can I make sure to keep the forked repo pipeline run in sync with original repo's pipeline.

Cc: @gaborbernat (Sorry for tagging, do let me know if there is a better way to communicate on such issues)

[gaborbernat]

Released via https://github.com/pypa/virtualenv/releases/tag/20.36.0