Fix update-cgmanifest.ps1 script to produce deterministic output

[Copilot]

Problem

The update-cgmanifest.ps1 script was regenerating the entire cgmanifest.json file each time it ran, causing the file to show changes in source control even when there were no actual changes to package versions or new packages added.

The script had several issues:

• Package registrations were added in the order they were processed (not alphabetical)
• JSON field ordering was inconsistent between runs
• Even with identical package versions, the file would appear modified in git

Solution

Modified the script to ensure deterministic, consistent output:

1. Sort package registrations alphabetically by package name before writing to JSON
2. Use ordered hashtables to ensure consistent field ordering within JSON objects
3. Maintain consistent JSON structure across multiple script runs

Changes Made

• Added sorting of $newRegistrations by package name: $newRegistrations | Sort-Object { $_.component.nuget.name }
• Implemented ordered hashtables using [ordered]@{} syntax to control field ordering
• Ensured consistent structure: type before nuget, name before version
• Maintained all existing functionality for package detection and version processing

Verification

Created comprehensive tests that verify:

• ✅ Multiple script runs produce identical output (zero diff)
• ✅ Packages are sorted alphabetically by name
• ✅ Field ordering is consistent within JSON objects
• ✅ No functional changes to package detection logic

Example Before/After

Before: Running the script twice would show differences like:

-          "name": "SQLitePCLRaw.bundle_green",
-          "version": "2.1.10"
+          "version": "2.1.10",
+          "name": "SQLitePCLRaw.bundle_green"

After: Running the script multiple times produces identical output with zero differences.

This resolves the issue where changes to cgmanifest.json files would appear in source control unnecessarily, making it easier to identify actual package version changes.

Fixes #30054.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.