Test: Move extensions, settings and devPort to vscode property

[chrmarti]

Refs: devcontainers/spec#1

• anyOS @aeschli
• anyOS @DonJayamanne

Complexity: 3

Create Issue

---

• Set up a dev container. E.g., have a workspace folder with a .devcontainer.json (or .devcontainer/devcontainer.json):

{
	"image": "mcr.microsoft.com/vscode/devcontainers/base:bullseye"
}

• Verify the "extensions", "settings" and "devPort" properties still work when used as top-level properties.
• Verify they also work when used as subproperties under "vscode" as the top-level property.
• Verify there is IntelliSense for both variations and that there is a warning when you use a property in both locations.

Note that when adding configuration files from the built-in definitions (templates), these are still using the older top-level properties, so we have time to roll out the support first.

[chrmarti]

(Removing verification-found as we use that to label bugs reopened due to failed verification, but not for testplan-items.)