Updated projects to net10.0 instead of net8.0

[martindevans]

• Updated projects to net10.0 instead of net8.0
• Updated nuget packages (some of these updates required net10)

[zsogitbe]

Thanks for the update, Martin!

To be honest, I’m a bit cautious about jumping to .NET 10.0 just yet. My personal take is that we should probably stick with .NET 8.0 for now. Since .NET 8 is a Long-Term Support (LTS) version, it ensures better stability and compatibility for more users.

Moving to .NET 10 might create an unnecessary barrier for people who aren't ready to update their environments yet. Unless there’s a specific feature in those new NuGet packages that we absolutely need, I’d prefer to stay on the LTS release.

[martindevans]

One of the package updates required upgrading to dotnet10, so that was the motivation to move. It wasn't a critical package though (not anything in the main project), so we could certainly just skip it package and remain on 8 for a while longer.

However, Dotnet 8 goes out of support in November 2026. We must move off 8 before then. The only choices are to upgrade to 10 (LTS) or upgrade to 11 (STS).

For now, I'm going to create a new PR with the easy to upgrade packages and stick to 8.

[martindevans]

Note: One of other option would be to multitarget .net8 and .net10 for a few months. We've previously decided against that because it increases the testing burden, which is already a major bottleneck! We could revisit that decision though.