For #4955 Implement Centralized Package Version Management for Solution

[leigh-pointer]

This PR introduces Centralized Package Version Management for the solution by utilizing the Directory.Packages.props file. This change ensures consistency in package versions across all projects in the solution, streamlining the package update process and reducing the risk of version conflicts.
Key Changes:

1. Centralized Package Version Management: Introduced Directory.Packages.props file to manage NuGet package versions at the solution level.

• All common NuGet package versions are now defined in this single file.
• Packages will be shared across all projects, ensuring the same version is used across the solution.

2. Simplified Package Updates: Now, package versions can be updated in one place, and all projects will automatically use the updated version when restoring packages.

3. Reduced Manual Updates: Eliminated the need to manually update NuGet package versions in each project's .csproj file.

Benefits:

• Consistency: Ensures that all projects within the solution use the same version of shared packages, preventing version mismatches and potential issues.
• Efficiency: Makes it easier to update NuGet package versions by only modifying the version in the Directory.Packages.props file, rather than in each individual project file.
• Scalability: Ideal for large solutions with multiple projects, as the package management is simplified and centralized.

[thabaum]

After testing the build process things worked fine, however, when I went to update the package through Visual Studio Nuget Package Manager I ran into an error:

There are 2 package sources defined in your configuration. When using central package management, please map your package sources with package source mapping (https://aka.ms/nuget-package-source-mapping) or specify a single package source. The following sources are defined: nuget.org, NuGetOrg

Since I never used CPM before this was a new issue for me to resolve.

In order to resolve it I had to go to %appdata%\Roaming\NuGet\NuGet.Config and edit the file removing the extra NuGetOrg entry so it only had one package source value as shown below:

<configuration>
  <packageSources>
    <add key="nuget.org" value="https://api.nuget.org/v3/index.json" protocolVersion="3" />
  </packageSources>
</configuration>

We may need to add some troubleshooting support in documentation to help others down the road with the same issue who may be unfamiliar with using this and run into the same issue.

[sbwalker]

I am closing this PR as I would prefer to not utilize centralized package management in Oqtane