[Bug] DevContainer doesn't start the temporal server image

When you open this repo in vscode you can optionally chose to run it in a devcontainer - which is fantastic! However all the images start apart from the auto-setup:latest container which I assume is the Temporal Server.

When I look in the logs of the failing container it mentions a missing file which I can confirm is not in the repo

config/dynamicconfig/development_es.yaml: no such file or directory

Temporal CLI address: 172.18.0.3:7233.
+ + grep -q temporal SERVING
operator cluster health
2023/06/08 16:12:22 Loading config; env=docker,zone=,configDir=config
2023/06/08 16:12:22 Loading config files=[config/docker.yaml]
{"level":"info","ts":"2023-06-08T16:12:22.452Z","msg":"Build info.","git-time":"2023-05-15T23:50:55.000Z","git-revision":"45d22540323e59e4cd3fd62139b73409f1264fb3","git-modified":true,"go-arch":"amd64","go-os":"linux","go-version":"go1.20.4","cgo-enabled":false,"server-version":"1.20.3","debug-mode":false,"logging-call-at":"main.go:143"}
Unable to create dynamic config client. Error: unable to validate dynamic config: dynamic config: config/dynamicconfig/development_es.yaml: stat config/dynamicconfig/development_es.yaml: no such file or directory

Minimal Reproduction

Open in Remote Containers and see if the Temporal Service is running.

Environment/Versions

• OS and processor: Windows running WSL and the DevContainer
• Latest from main

Start by inspecting the devcontainer configuration and the container command that loads config/docker.yaml; verify how config/dynamicconfig/development_es.yaml is expected to be supplied. Reproduce with Open in Remote Containers and confirm the Temporal service starts without the missing-file error.