Use central package management

[Kryptos-FR]

PR Details

https://learn.microsoft.com/en-us/nuget/consume-packages/central-package-management

Description

Adds Directory.Packages.props and references all package versions there.

Related Issue

Discussed on Discord.

Motivation and Context

Prevent out-of-sync dependencies between projects.

Types of changes

• Docs change / refactoring / dependency upgrade
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist

• My change requires a change to the documentation.
• I have added tests to cover my changes.
• All new and existing tests passed.
• I have built and run the editor to try this change out.

[Kryptos-FR]

Note: this is a bit hackish but necessary because the Directory.Packages.props gets imported later, and the build complains if we try to use Version nonetheless.

[xen2]

LGTM!
I ran it and double-check the nuget resolver result (on GameStudio only) to check if no package unintentionally changed/added/removed: it was all good.
Great change, thanks again.

[Kryptos-FR]

Thanks for the review @xen2. I have resolved the conflict from latest master.

[xen2]

Noticed a small issue when building package:
https://teamcity.stride3d.net/buildConfiguration/Package_BuildPackage/23697?hideProblemsFromDependencies=false&hideTestsFromDependencies=false&expandBuildDeploymentsSection=true&expandBuildChangesSection=true&expandBuildProblemsSection=true&guest=1

deps\Stride.GitVersioning\Stride.GitVersioning.csproj : error NU1008: Projects that use central package version management should not define the version on the PackageReference items but on the PackageVersion items: Microsoft.Build.Utilities.Core;LibGit2Sharp.

[Kryptos-FR]

Should be fixed by the other PR that moved the props file #2055 to avoid conflicts with deps.