feat: add devcontainer

[nbmaiti]

-> Add devcontainer configuration for development environment setup.
-> Added go debug

[Copilot]

Pull request overview

This PR adds devcontainer configurations to standardize the development environment for the project. It includes setup for both standard and MEI device development scenarios, along with improved Go debugging capabilities.

Changes:

• Added two devcontainer configurations: one for standard development without MEI device and one for MEI device development on Linux hosts
• Enhanced VS Code launch configurations with dynamic input variables for server address, profile name, and DNS suffix
• Removed asRoot parameter from all Go debug configurations in launch.json

Reviewed changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated 2 comments.

Show a summary per file

File	Description
.vscode/launch.json	Updated Go debug configurations to use input variables and removed deprecated asRoot settings
.devcontainer/standard/devcontainer.json	Added standard devcontainer configuration with Go 1.25 and proxy support
.devcontainer/pre-create.sh	Added pre-creation script to check/install Intel LMS service on the host
.devcontainer/post-create.sh	Added post-creation script for proxy configuration and Go tool installation
.devcontainer/mei/devcontainer.json	Added MEI device devcontainer with privileged access and host networking

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[graikhel-intel]

Thanks for doing this @nbmaiti!

One suggestion to make this easier to review, it might help to split this into two PRs.

• One PR for the launch.json changes (dynamic inputs), which looks straightforward and we should be able to merge that quickly.

• A second PR focused on the devcontainer additions.

For the devcontainer piece specifically, the current config appears to be Linux only. On Windows hosts, VS Code will still prompt users to reopen in a dev container, but the flow itself won’t work for them. This could be confusing for Windows based contributors, especially since many of our developers (and customers) still use Windows. I just want to make sure we’re aligned on the intended developer experience before merging this part.

[nbmaiti]

Thanks for doing this @nbmaiti!

One suggestion to make this easier to review, it might help to split this into two PRs.

• One PR for the launch.json changes (dynamic inputs), which looks straightforward and we should be able to merge that quickly.
• A second PR focused on the devcontainer additions.

For the devcontainer piece specifically, the current config appears to be Linux only. On Windows hosts, VS Code will still prompt users to reopen in a dev container, but the flow itself won’t work for them. This could be confusing for Windows based contributors, especially since many of our developers (and customers) still use Windows. I just want to make sure we’re aligned on the intended developer experience before merging this part.
"reopen in container" will come when devcontainer extension is installed only

• updated PR with only devcontainer changes.
• Added comment/name on limited LME support on windows

[Copilot]

Pull request overview

Copilot reviewed 4 out of 4 changed files in this pull request and generated 8 comments.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.