1. Does this PR affect any open issues?(Y/N) and add issue references (e.g. "fix #123", "re #123".):
[X] N
[ ] Y
2. What is the scope of this PR (e.g. component or file name):
.devcontainer.json
3. Provide a description of the PR(e.g. more details, effects, motivations or doc link):
update .devcontainer.json with kusion quick start env, so that the vscode-kusion can recognize it and provider user friendly hint for minikube interaction in quick start
[ ] Affects user behaviors
[ ] Contains syntax changes
[ ] Contains variable changes
[ ] Contains experimental features
[ ] Performance regression: Consumes more CPU
[ ] Performance regression: Consumes more Memory
[ ] Other
4. Are there any breaking changes?(Y/N) and describe the breaking changes(e.g. more details, motivations or doc link):
[X] N
[ ] Y
5. Are there test cases for these changes?(Y/N) select and add more details, references or doc links:
[ ] Unit test
[ ] Integration test
[ ] Benchmark (add benchmark stats below)
[ ] Manual test (add detailed scripts or steps below)
1. Does this PR affect any open issues?(Y/N) and add issue references (e.g. "fix #123", "re #123".):
2. What is the scope of this PR (e.g. component or file name):
.devcontainer.json
3. Provide a description of the PR(e.g. more details, effects, motivations or doc link):
update .devcontainer.json with kusion quick start env, so that the vscode-kusion can recognize it and provider user friendly hint for minikube interaction in quick start
4. Are there any breaking changes?(Y/N) and describe the breaking changes(e.g. more details, motivations or doc link):
5. Are there test cases for these changes?(Y/N) select and add more details, references or doc links:
6. Release note
Please refer to Release Notes Language Style Guide to write a quality release note.