moon v2 and toolchains are using executables from proto/tools directory

Since moon v2 there is a strange behaviour. When installing a tool via moon v2 toolchains tier3 and executing the command, it will take the exe from the proto/tools directory instead of the `proto/shims` and `proto/bin` folder. Example: When using matlab (own proto plugin and moon toolchain) it will execute it `matlab` from C:\Users\xxx\.proto\tools\matlab\R2022b\matlab.exe instead of C:\Users\xxx\.proto\shims\matlab.exe When installing python we have also 3 different incidents:- 1) Same incident as above, so the task is (Yes I know the syntax is incorrect ;)) ``` python-version: command: python -version options: cache: false ``` Produces ``` python -version (in workspace) Unknown option: -e usage: C:\Users\xxx\.proto\tools\python\3.11.13\python.exe [option] ... [-c cmd | -m mod | file | -] [arg] ... Try `python -h' for more information. ``` So my expectation would be to take it from shims, if not available take from bin (both paths are available in PATH) 2) Python shall take it from generated ".venv" folder So esp. on the python toolchain it shall take the `$workspaceRoot/.venv/[bin/Scripts]/python` 3) The python toolchain can install via pip the dependencies from requirements.txt So with the 2 incidents above the dependencies will be installed into `C:\Users\xxx\.proto\tools\python\3.11.13` and not the `.venv` folder. @milesj: Do you have an idea why we have now this strange behaivour?