Compose code lens do not work for files that are outside the workspace

[rcjsuen]

Not quite sure if this should go here or in microsoft/compose-language-service... 🤔

1. Open a folder.
2. Open a compose.yaml in a different folder that is under the current folder.
3. Use code lens to run the service.
4. An error occurs.

2025-06-06-compose-codelens-error.mov

$ code -v
1.100.3
258e40fedc6cb8edf399a463ce3a9d32e7e1f6f3
arm64

$ code --list-extensions --show-versions
amodio.tsl-problem-matcher@0.6.2
asvetliakov.vscode-neovim@1.18.22
bierner.markdown-mermaid@1.28.0
dbaeumer.vscode-eslint@3.0.10
docker.docker@0.8.1
eamodio.gitlens@17.1.1
esbenp.prettier-vscode@11.0.0
github.vscode-github-actions@0.27.2
golang.go@0.46.1
ms-azuretools.vscode-containers@2.0.3
ms-vscode-remote.remote-containers@0.413.0
ms-vscode.makefile-tools@0.12.17
redhat.vscode-yaml@1.18.0

[bwateratmsft]

IMO the best solution would be to utilize the workspaceFolders request to ask the client what workspace folders are open, and ensure the current compose document is in one of them. If it is not, then we should not show the code lenses.

If the client does not support the workspaceFolders request, we should arguably not show code lenses at all...or maybe do show them. IDK.