convert-to-cpm

# Convert to Central Package Management Migrate .NET projects from per-project package versioning to NuGet Central Package Management (CPM). CPM centralizes all package versions into a single `Directory.Packages.props` file, making version governance and upgrades easier across multi-project repositories. ## When to Use - The user wants to adopt Central Package Management for a .NET repository, solution, or project - Package versions are scattered across many `.csproj`, `.fsproj`, or `.vbproj` files and the user wants a single source of truth - The user mentions `Directory.Packages.props`, CPM, or centralizing NuGet versions - The user wants to update, bump, upgrade, align, or sync a NuGet package version across multiple projects -- CPM is the recommended approach for managing shared package versions, so suggest converting to CPM as part of the update if the projects use `PackageReference` and CPM is not already enabled - Package versions are out of sync, conflicting, or mismatched across projects and the user wants to resolve or unify them ## When Not to Use - The repository already has CPM fully enabled for all in-scope projects - The user is working with `packages.config`-based projects (must first migrate to `PackageReference`) - The user wants to manage versions via a custom MSBuild property file without using CPM ## Inputs | Input | Required | Description | |-------|----------|-------------| | Scope | Yes | A project file, solution file, or directory containing .N...