Navigating VSCode Workspaces with AWS Toolkit

## System details (run `AWS: About` and/or `Amazon Q: About`)

- OS: MacOS
- Visual Studio Code version: 1.107.1
- AWS Toolkit version: 3.89.0
- Amazon Q version: N/A

## Question

I develop ML code in EC2 instances; therefore there are multiple projects and workspaces in my EC2 instance. I want to be able to focus on specific directories / workspaces in my explorer view. VSCode does this through remote-ssh; every new directory needs its own ssh connection.

This breaks with how AWS Toolkit modifies ~/.ssh/config, as it adds `Host aws-ec2-*` and the proxy command to ec2_connect. When trying to open a new workspace, remote-ssh will hang as it tries to use the proxy, but it lacks the environment variables:

eg: ./ec2_connect: line 19: LOG_FILE_LOCATION: unbound variable,
which leads to:Connection closed by UNKNOWN port 65535

Naturally I can use remote-ssh to directly connect to my EC2 instance, but I am asking whether there is a workaround specifically with aws toolkit and this issue / feature request if this was not considered. Personally this is very frustrating to be unable to do, only being able to work in the initial root directory that aws toolkit connects me to.

I am one of few computational developers for my research group, so getting them to connect with toolkit instead of teaching others how to set up ssh config would be much easier.

Start by reviewing the generated ~/.ssh/config entries for Host aws-ec2-* and the ./ec2_connect script, especially line 19 where LOG_FILE_LOCATION is referenced. Reproduce the failure by opening another VSCode Remote-SSH workspace from an AWS Toolkit connection. Done means separate directories or workspaces can be opened without the proxy connection hanging or closing.

Written by the indexing model from the issue text.