You can avoid the awfulness of chocolatey by sticking with WSL2. Install that, docker desktop, windows terminal and vscode, voila you are back in linux land and can completely avoid powershell and windows broken file names.
If you avoid PowerShell, go back to where you came from :) Avoid bad advices.
Windows itself has reached a dead end. It is such a mishmash of incompatible tech that Microsoft themselves have stopped trying to fix their admin GUI interface. Between registry, Com and Dcom and even a few leftover text files, there is no way to configure a windows system consistently.
Powershell is an over complicated band-aid to cover it up, ignoring that the wound underneath has become septic.
I get that they had to do something to drag it together, but even good powershell scripts end up as 4 different coding styles crammed together, depending on what component CLI output or interface you are trying to use.
WSL2 is a great thing if you need to do anything with python, node and even .NET. All the online tutorials work and since everything is a CLI these days, why not use a decent shell that doesn't have windows legacy character escape bogosity, broken file names and has sane argument handling?