When running commands in terminal view, extension takes PATH env variable and put cli tool location as first entry (${pathToToolFolder}${pathSeparator}${currentPathValue}) then pass modified PATH env variables through TerminslOptions instance to terminal to run with.
This does not work when system PATH var already has folder with the cli tool in it but with different version. In this case system PATH always searched first and cli tool extension wants to execute never gets executed, cli tool from system PATH env var is always executed insted.
The only way to make sure the extension runs specific cli tools is to use absolute path when running in terminal.
When running commands in terminal view, extension takes PATH env variable and put cli tool location as first entry (${pathToToolFolder}${pathSeparator}${currentPathValue}) then pass modified PATH env variables through TerminslOptions instance to terminal to run with.
This does not work when system PATH var already has folder with the cli tool in it but with different version. In this case system PATH always searched first and cli tool extension wants to execute never gets executed, cli tool from system PATH env var is always executed insted.
The only way to make sure the extension runs specific cli tools is to use absolute path when running in terminal.