fix: write Windows config to ProgramData and reseed per-user trays

[madhavilosetty-intel]

Write the machine config to %ProgramData% (the console's Windows machineConfigPath) so each user's tray seeds from it, clear stale per-user config on (re)install, and remove every profile's per-user data on uninstall.

[Copilot]

Pull request overview

Updates the Windows NSIS installer/uninstaller for the Console to seed configuration from a machine-wide location (%ProgramData%) so each user’s system tray can re-seed from a common config, and to more aggressively clear per-user state during reinstall/uninstall flows.

Changes:

• Write the generated config.yml to %ProgramData%\device-management-toolkit\config.yml via SetShellVarContext all.
• On install/reinstall, delete each profile’s per-user config.yml so trays will re-seed from the machine config.
• On uninstall (when opting in), remove per-user data directories for every profile, and remove the machine-wide config seed.

---

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

[graikhel-intel]

I've tested this on Windows 11, and everything looks good from my testing.

Here's what I verified:

• Started with a clean system by ensuring all previous installation artifacts were removed (configuration, databases, logs, and any leftover data).
• Performed a fresh install and verified that the application was configured correctly.
• Confirmed the following locations:
  • Config and database: %APPDATA%\device-management-toolkit
  • Logs: %LOCALAPPDATA%\device-management-toolkit
  • Executable and uninstaller: C:\Program Files\device-management-toolkit\Console
• Performed an uninstall and verified that all application files and data were cleaned up successfully.

---

A couple of items that might be worth considering for a future enhancement (perhaps Q3'26):

• We intentionally place the TLS certificates in the temporary directory today since customers are expected to replace them with their own certificates. This might be a good opportunity to revisit whether they should instead live under the application config directory or another more appropriate location.

• Is there a way to customize the installer icon as well as the application icon? It would help make the installer feel more polished.

• With the upcoming "Windows Credential Manager" secure storage feature, we have an opportunity to have the installer store the configured credentials directly in the Credential Manager instead of the config.

Other than that, great job getting this done!