Document Microsoft.Data.Sqlite .NET Framework support removal in EF Core 11 breaking changes

[Copilot]

Adds the missing EF Core 11 breaking-change note for Microsoft.Data.Sqlite support on .NET Framework. The doc now makes the platform change explicit and calls out the 10.0.x servicing line as the path for apps that must remain on .NET Framework while continuing to pick up SQLite CVE fixes shipped there.

• Breaking change entry

  • Adds a new Microsoft.Data.Sqlite item to the EF Core 11 breaking-changes summary table.
  • Introduces a dedicated section covering old behavior, new behavior, rationale, and mitigation guidance.

• Support boundary clarification

  • Documents that Microsoft.Data.Sqlite / Microsoft.Data.Sqlite.Core previously flowed through netstandard2.0, which allowed .NET Framework consumption.
  • Clarifies that 11.0 targets net10.0 only, so .NET Framework apps can no longer move forward to 11.0.

• Migration guidance

  • Recommends moving to .NET 10+ where possible.
  • Explicitly directs .NET Framework users who cannot migrate yet to stay on the latest 10.0.x servicing release.

• Servicing/CVE note

  • Captures the important nuance behind the issue: the 10.0.x line already uses SQLite3MC.PCLRaw.bundle, so staying on that line remains the practical way to receive ongoing bundled SQLite security fixes without moving off .NET Framework immediately.

#### Microsoft.Data.Sqlite no longer supports .NET Framework

Starting with Microsoft.Data.Sqlite 11.0, both packages target `net10.0` only.

If you must remain on .NET Framework, stay on the latest Microsoft.Data.Sqlite 10.0.x servicing release.

[Copilot]

Pull request overview

Adds a missing EF Core 11 breaking-change entry documenting that Microsoft.Data.Sqlite drops .NET Framework compatibility, and provides rationale plus mitigation guidance for apps that can’t yet migrate off .NET Framework.

Changes:

• Adds a new breaking-change row for “Microsoft.Data.Sqlite no longer supports .NET Framework” to the Microsoft.Data.Sqlite summary table.
• Introduces a dedicated Medium-impact breaking-change section describing old/new behavior, rationale, and mitigations.