Add migration analysis for Windows Nano Server

[ElmansVW]

The new documentation file NANO_SERVER_MIGRATION_ANALYSIS.md details the specific blockers preventing migration to Windows Nano Server. These include:

• Dependency on .NET Framework 4.8 (Nano supports .NET Core/.NET 5+)
• Heavy usage of System.Activities (Windows Workflow Foundation), which is not available in .NET Core.
• Reliance on COM Interop and other Windows-specific APIs like System.DirectoryServices and WMI, which have limited or no support in Nano Server.
• Use of legacy web technologies (System.Web).

The document concludes that a rewrite to .NET Core/5+ would be necessary to support Nano Server, making this a high-effort modernization task rather than a simple platform migration.

---

PR created automatically by Jules for task 18091324924383957816 started by @ElmansVW

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.