Provide the option to resolve relative workspace path as symlinked path, not real path

Hi,

This issue is a follow-up issue for those following issues:

- https://github.com/docker/for-win/issues/14380
- https://github.com/microsoft/vscode-remote-release/issues/10301

So the problem is following, somehow docker CLI doesn't like to mount folders, which are mount to WSL at same time. However if this folder like `/mnt/wsl/workspace` symlinked to something like `~/workspace` , then when I mount it from ~/workspace - it works. However it doesn't work in VS Code, because it still resolves path to real path.

So I tried to test it just with devcontainers CLI and here is what I see:

If I run like this:

```
cd ~/workspace
devcontainer up --workspace-folder .
```

Then it doesn't work. It means that container is up and running, but workspace folder in the devctontainer is empty - there are no files. In Docker Desktop I can see that it resolves . into /mnt/wsl/worspace

However when I run the command like this:
```
devcontainer up --workspace-folder /home/myuser/workspace
```

Then devcontainer is up but also files are there. In the Docker Desktop I can see that the path is not changed.

So what I'd like CLI to do - whenever I provide a relative path like ., can it please follow cwd where I am in and not resolve it to a real path?