Add .NET 10 / EF Core 10 / AutoMapper 16 support

[xrkolovos]

Summary

• Add net10.0 target framework alongside existing net8.0 and net9.0
• Update AutoMapper to 16.x, AutoMapper.Collection to 13.x, ExpressionMapping to 10.x
• Use per-TFM EF Core references (8.0.16 / 9.0.7 / 10.0.5) since EF Core 10 only supports net10.0
• Update test dependencies: FluentAssertions 8.9.0, xunit 2.9.3, Microsoft.NET.Test.Sdk 18.3.0
• Update tooling: Roslynator 4.15.0, MinVer 7.0.0
• Add setup-dotnet step to CI/release workflows for all required SDKs

Test plan

• Build succeeds for all 3 TFMs (net8.0, net9.0, net10.0)
• All 180 tests pass (60 per TFM)
• CI pipeline passes with .NET 10 SDK setup

[xrkolovos]

@dotnet-policy-service agree company="egritosgroup"

[xrkolovos]

@jbogard who can check and accept this?
thank you

[aarondglover]

@jbogard who can check and accept this? thank you

@jbogard I am blocked without this package supporting v16

[aarondglover]

@xrkolovos can you request a PR review from Jimmy?

[xrkolovos]

@lbargaoanu @Nicot3 can you merge this pr? thank you

[Nicot3]

@xrkolovos I've just have a quick look without testing or building but, it is possible to add more versions? For example, AutoMapper.Extensions on version 12 is compatible with .NET 10, and with this change is not going to be possible to use this version anymore. This will force update to some people that maybe don't need to update his dependencies.

I'm not 100% sure anyways, need to investigate a bit more or get a second opinion 😄

[ahmed-abdelrazek]

merge so people can update and avoid the new security vulnerability then solve your dependencies issues in another pr @Nicot3

[xrkolovos]

@xrkolovos I've just have a quick look without testing or building but, it is possible to add more versions? For example, AutoMapper.Extensions on version 12 is compatible with .NET 10, and with this change is not going to be possible to use this version anymore. This will force update to some people that maybe don't need to update his dependencies.

I'm not 100% sure anyways, need to investigate a bit more or get a second opinion 😄

do this with a seperated pull request

@Nicot3 it will be a realease soon?

[Nicot3]

@xrkolovos I don't have permissions on the repo, I can just approve 😅