Allow configuring SCP similar to `Remote.SSH: Path` setting

Did a quick search for SCP and did not find a similar request. Please allow us to configure the SCP path similar to SSH path.

That will solve several issues when using WSL. I want my SSH/SCP connections to happen through WSL, not directly through Windows. I can do that for SSH via setting the path setting. Using an ssh-helper.bat script below.
ssh-helper.bat

C:\Windows\system32\wsl.exe ssh %*

There is no option to do so for SCP so I have to disable Local Server Download.

Full Context
I am using DevSpaces in WSL to create remote development containers inside of my Kubernetes cluster. DevSpaces can be configured to setup a remote ssh server inside of the pod and saves the credentials locally in wsl. Here is the workaround I have to do to get this functioning.

• For ease of use, I symlink my ~/.ssh/config in WSL to my Windows host
• Set VSCode SSH Extension setting Remote.SSH: Path to the full path to ssh-helper.bat (contents above)
• Set VSCode SSH Extension setting Remote.SSH: Local Server Download to off.
• Set VSCode SSH Extension setting Remote.SSH: Enable enableDynamicForwarding to off.
• In remote container, make sure curl/wget is available for downloading.

With this I can start the devspace from my WSL instance. Connect from VSCode which is using RemoteSSH.

Start by reading how the existing Remote.SSH: Path setting is handled and tracing where SCP is invoked. Use the provided ssh-helper.bat example as the desired WSL wrapper. Done means SCP has a configurable path so transfers can run through WSL without disabling Local Server Download.