Respect config generated by `config-ssh`

[code-asher]

I am not sure how feasible this is, but it seems more doable now that config-ssh uses wildcards. We generate a separate config because we want to add flags and options. Maybe we could read the SSH config and add anything we are missing? Would need to respect CODER_SSH_CONFIG_FILE as well.

Or, can we do something with includes? Or if we use a prefix like coder.vscode.* then it will just naturally inherit options.

[matifali]

We now use wildcard configs as per version 1.4.0. This should be fixed. If not, please comment/reopen.

[code-asher]

The problem was that users would do things like coder config-ssh -o ForwardX11=yes and ForwardX11=yes will apply to coder ssh or ssh coder.* but it will not apply to the extension, wildcards or no.

It can be worked around by manually adding ForwardX11=yes to the SSH config file or the extension settings, but it could be nice to support it automatically. Not sure how many people care about this though.