DateOnlyAndTimeOnlyTypes: net10.0 and EF Core 10 native DateOnly/TimeOnly mapping

[vladimir-pecanac-main]

Updates the sample for the article "How to Map DateOnly and TimeOnly to SQL Server in EF Core" (https://code-maze.com/csharp-map-dateonly-timeonly-types-to-sql/).

Only dotnet-efcore/DateOnlyAndTimeOnlyTypes changes.

• Both projects move from net7.0 to net10.0. Every Microsoft.EntityFrameworkCore.* and Microsoft.Extensions.* package goes from 7.0.0 to 10.0.13 (newest 10.0.x on NuGet, 2026-10-17).
• System.Security.Cryptography.Pkcs 10.0.13 is referenced directly. EF Core SqlServer 10.0.13 brings Microsoft.Data.SqlClient 6.1.7, which brings Pkcs 9.0.11, and without the direct reference restore reports NU1902 (GHSA-2fmv-rv2c-59x7) and NU1903 (GHSA-846f-f764-76mx).
• Test packages: xunit 2.9.3, xunit.runner.visualstudio 4.0.1, Microsoft.NET.Test.Sdk 18.11.0, coverlet.collector 10.1.0.
• AppDbContext: ConfigureConventions is gone, because EF Core 8 and later map DateOnly to date and TimeOnly to time on SQL Server. A parameterless constructor sits beside the options constructor, so dotnet ef migrations add can create the context.
• TimeOnlyConverter, DateOnlyComparer and TimeOnlyComparer are deleted. DateOnlyConverter stays, for the legacy datetime2 column case the article keeps.
• New migration RemoveDateOnlyTimeOnlyConverters (empty Up and Down, scaffolded with dotnet-ef 10.0.13) and the updated model snapshot. dotnet ef migrations has-pending-model-changes: no changes.
• Tests: the round trip (now with a 16:30 end time), the date/time schema mapping, the DATEPART translation of a filter, and the legacy datetime2 converter case via a test-only LegacyAppDbContext. None needs a database, and no test name contains Live.

Local run on SDK 10.0.302, runtime 10.0.10: build 0 warnings 0 errors, dotnet test Passed 4 Failed 0.