venv created by poetry seems to 'hide' pip resulting in mixed languages error message and weird characters.

Poetry
Version: 1.5.1
Python: 3.11.0

Virtualenv
Python: 3.11.3
Implementation: CPython
Path: D:\HDD_Code\Django_SANDBOX.venv
Executable: D:\HDD_Code\Django_SANDBOX.venv\Scripts\python.exe
Valid: True

System
Platform: win32
OS: nt
Python: 3.11.3
Path: C:\Python311
Executable: C:\Python311\python.exe

Windows 11

pyproject.toml: https://github.com/biofsphere/Django_SANDBOX/blob/main/pyproject.toml

[X] I am on the latest stable Poetry version, installed using a recommended method.
[X] I have searched the issues of this repo and believe that this is not a duplicate.
[X] I have consulted the FAQ and blog for any relevant entries or release notes.
[X] If an exception occurs when executing a command, I executed it again in debug mode (-vvv option) and have included the output below.

Fatal error in launcher: Unable to create process using '"D:\HDD_Code\SANDBOX.venv\Scripts\python.exe" "D:\HDD_Code\Django_SANDBOX.venv\Scripts\pip.exe" -V -vvv': O sistema n�o pode encontrar o arquivo especificado.

Issue

The error message above indicates pip can't be found. However, I checked libs and it is there. In addition, I get this mixed language error message with a weird character in the Portuguese word 'não' (last portion of the message). I also checked PATH and python/scripts are there too. Moreover, I tested another venv created with 'python -m venv venv' and under this venv the command 'pip -V' correctly runs outputting pip's version number. I can only assume the virtual environment created with Poetry is leading to these weird behavior.

I tested multiple alternatives to fix the weird character with no success (e.g., setting UTF-8 in PowerShell, or chcp to 1252). Nothing seems to fix this. I look forward to further understanding this issue. Thank you.

Reproduce the report on Windows 11 with Python 3.11.3 and Poetry 1.5.1, comparing a Poetry-created .venv with one made by python -m venv, then inspect the referenced pyproject.toml and the .venv\Scripts\pip.exe invocation. Done means identifying why pip cannot launch and why the error contains the mixed-language and malformed character output, with a verified corrective change or clear reproduction findings.