"Exec in CLI" option does not start into code folder, namely `com.docker.devenvironments.code`

Describe the bug

Instead of starting a VSCode session, I want to fast inspect my code so I start into a CLI, but the folder it opens is not the work directory for the code.

To Reproduce

Steps to reproduce the behavior:

create a dev environment from sample: https://github.com/dockersamples/single-dev-env
when ready, use "Exec in CLI" instead of opening it in VSCode
```
$ pwd
/go
```

Expected behavior I expected my working directory would be set to same one as VSCode opens, namely com.docker.devenvironments.code (unless changed)

Screenshots not needed

Desktop (please complete the following information):

OS: Windows 10 Pro
Version 21H2 with latest updates

Version of Docker Desktop:
You can find the version by clicking on the About Docker Desktop menu

Docker Desktop Version 4.5.1 (74721)

Additional context none currently I am aware of

docker / dev-environments

"Exec in CLI" option does not start into code folder, namely `com.docker.devenvironments.code` #104