Update Pomelo MySQL to v9 Preview

[bgrainger]

Description

This removes use of the legacy global 'MySqlConnectorLogManager.Provider' and uses Microsoft.Extensions.Logging (via MySqlDataSource).

Needed to add VersionOverride for multiple packages due to Microsoft.EntityFrameworkCore.Relational v9.0.0.

Needs MySqlConnector.* 2.4.0 and Pomelo.EntityFrameworkCore.MySql 9.0.0-preview.2.efcore.9.0.0 to be added to approved packages list.

Checklist

• Is this feature complete?
  • Yes. Ready to ship.
  • No. Follow-up changes expected; needs to update to RTM version of Pomelo.
• Are you including unit tests for the changes and scenario tests if relevant?
  • Yes
  • No; no changes to existing package functionality.
• Did you add public API?
  • Yes
    • If yes, did you have an API Review for it?
      • Yes
      • No
    • Did you add <remarks /> and <code /> elements on your triple slash comments?
      • Yes
      • No
  • No
• Does the change make any security assumptions or guarantees?
  • Yes
    • If yes, have you done a threat model and had a security review?
      • Yes
      • No
  • No
• Does the change require an update in our Aspire docs?
  • Yes
    • Is this introducing a breaking change?
      • Yes
        • Link to aspire-docs issue (please use this breaking-change template):
      • No
        • Link to aspire-docs issue (please use this doc-idea template):
  • No

Microsoft Reviewers: Open in CodeFlow

[sebastienros]

I see two problems so far, but someone should confirm.
This is a preview dependency, the Aspire package is stable and can't reference/ship with a preview.

This version targets net8.0 only and it lifts EF core 9.0 only. Meaning an application targeting net8.0 will take a dependency on STS packages. See what npgsql did between 9.0.0 and 9.0.1 to fix that by introducing two TFMs in the package to point to efcore 8.0 and efcore 9.0 based on the targets.

[bgrainger]

This is a preview dependency, the Aspire package is stable and can't reference/ship with a preview.

I noted this in the PR checklist, but should have made this a "Draft" PR to be explicit: I don't expect this to be merged until Pomelo goes RTM.

This version targets net8.0 only and it lifts EF core 9.0 only. Meaning an application targeting net8.0 will take a dependency on STS packages. See what npgsql did between 9.0.0 and 9.0.1 to fix that by introducing two TFMs in the package to point to efcore 8.0 and efcore 9.0 based on the targets.

I'm not following yet (perhaps because I'm less familiar with EFCore than ADO.NET). It looks like Npgsql.EntityFrameworkCore.PostgreSQL 9.0.x depends only on EFCore 9; it doesn't have multiple TFMs? https://www.nuget.org/packages/Npgsql.EntityFrameworkCore.PostgreSQL/9.0.1#dependencies-body-tab

[bgrainger]

Oh, you're talking about here?

aspire/eng/Versions.props

Line 65 in 3991282

<NpgsqlEntityFrameworkCorePostgreSQLPackageVersion>8.0.11</NpgsqlEntityFrameworkCorePostgreSQLPackageVersion>

aspire/eng/Versions.props

Line 91 in 3991282

<NpgsqlEntityFrameworkCorePostgreSQLPackageVersion>9.0.0</NpgsqlEntityFrameworkCorePostgreSQLPackageVersion>

[sebastienros]

Right. Check this PR for instance after such a change in the library was done.

[sebastienros]

another option is to have a version for each TFM, and keep all the things net8.0 and net9.0 separate. This is what is bound to happen with npgsql for now since there is an issue when using npgsql:9.0 targeting EF 8.