Correct Windows enterprise policy Step 2 guidance to ADMX/GPO workflow

[Copilot]

The Windows section in docs/enterprise/policies.md incorrectly used macOS plist XML examples in “Step 2: Configure policy values,” which conflicted with the ADMX-based Windows deployment model. This PR aligns Step 2 with actual Windows policy administration via GPO/MDM.

• Scope

  • Updated Windows Step 2: Configure policy values in:
    • docs/enterprise/policies.md
    • docs/enterprise/policies.template.md
  • Kept rendered doc and template content in sync.

• What changed

  • Removed plist-style XML key/value examples (<key>, <string>, <true/>, <false/>) from the Windows section.
  • Replaced with ADMX administration guidance:
    • Configure via Group Policy Editor (gpedit.msc) under Computer Configuration > Administrative Templates > Visual Studio Code
    • Or configure via MDM/Intune administrative templates
    • Use Enabled/Disabled states and policy UI value fields
    • Leave policies Not Configured when not enforced
  • Added explicit registry backing path: Software\Policies\Microsoft\VSCode.

• Before/after example

  <!-- removed from Windows Step 2 -->
  <key>AllowedExtensions</key>
  <string>{"microsoft": true, "github": true}</string>
  
  <key>EnableFeedback</key>
  <true/>

  # replaced with
  Configure the imported VS Code ADMX policies in Group Policy Editor or Intune.
  Values are set in policy UI and written under Software\Policies\Microsoft\VSCode.