Support ssh-agent/gpg-agent/git credentials forward from Windows when using WSL path

[chrmarti]

Just out of curiosity. I do a slightly different approach. I have a devcontainers recipe which provides a volume for the project.
In it, I clone the project from git.

This way I keep my ssh, git and pgp things in windows, and all are forwarded to the devcontainer nicely (ssh-agent service enabled).

But when running from WSL2 filesystem, VSCode is using ssh, git and pgp from the distro the devcontainers folder is hosted in.

I find it a bit annoying, not to have an option to tell VSCode to always use my gitconfig, ssh config, know_hosts and agent, and pgp from Windows, like it does for devcontainers folder hosted on windows fs.

For everybody having all setup in Windows, I think it would do a huge help to have that switch, as the official docs already provide perfect guidance how to prepare your windows host for devcontainers. It simply breaks the minute u have the folder in wsl2...

Can you postpone and work on using also ssh, git and pgp from wsl2 after u allow people that completed all settings according to the current official docs to benefit of this automation from both windows fs and wsl fs?

Originally posted by @madalinignisca in #3902 (comment)

[chrmarti]

We now first check if we can forward to WSL and if not, try to forward to Windows. Similarly when connected through an SSH server. This was implemented as part of #2994.