Dependencies: Fixed dependency conflicts when installing Microsoft.EntityFrameworkCore.Design (closes #20421)

[lauraneto]

Fixes #20421

Changes

• Reference Microsoft.CodeAnalysis.CSharp.Workspaces and Microsoft.CodeAnalysis.Workspaces.MSBuild directly from the Umbraco.Infrastructure project to ensure that specific versions are used.
• Disable CPM (Central Package Management) in the Umbraco.Web.UI project, as that can sometimes hide dependency issues consumers might encounter.
• Remove references to packages that were not needed.

In order to reproduce the initial issue, simply create a new project in v16 and try to install Microsoft.EntityFrameworkCore.Design.

Additional PRs will follow that will target v17 and v13. A PR should also be done to the docs to remove the workaround.

[Copilot]

Pull Request Overview

This PR fixes dependency conflicts that occur when installing Microsoft.EntityFrameworkCore.Design in Umbraco projects by reorganizing how Microsoft CodeAnalysis packages are referenced and managed.

• Moves CodeAnalysis package references from Umbraco.Web.UI to Umbraco.Infrastructure to ensure proper version control
• Disables Central Package Management (CPM) in the Web UI project to expose potential dependency issues to consumers
• Removes unnecessary package references and centralizes dependency management

Reviewed Changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.

File	Description
src/Umbraco.Web.UI/Umbraco.Web.UI.csproj	Disables CPM, simplifies package references, and specifies explicit versions for EF Core Design and ICU runtime
src/Umbraco.Infrastructure/Umbraco.Infrastructure.csproj	Adds direct references to Microsoft.CodeAnalysis packages to prevent conflicts
Directory.Packages.props	Removes unused CodeAnalysis package versions from central management