.NET: Update to .NET 10 SDK

[Youssef1313]

Motivation and Context

Description

Contribution Checklist

• The code builds clean without any errors or warnings
• The PR follows the Contribution Guidelines
• All unit tests pass, and I have added new tests where possible
• Is this a breaking change? If yes, add "[BREAKING]" prefix to the title of the PR.

[Copilot]

Pull Request Overview

This PR attempts to update the .NET SDK from version 9.0 to 10.0 by modifying the GitHub workflow configuration. However, the update is incomplete as it only changes the dotnet-format.yml workflow file while leaving other workflow files, project files, and build configuration files still targeting .NET 9.0.

Key changes:

• Updates the .NET SDK version in the dotnet-format.yml workflow from "9.0" to "10.0"

[DeagleGross]

We already have a PR for .NET10 update: #2128

[Youssef1313]

@DeagleGross Yup, I had a chat with @rogerbarreto about it. The other PR does much more than updating .NET SDK though and I don't know when it will be finalized. So this PR is a subset of the other. If the other PR got merged first, this one can be closed.

[DeagleGross]

This PR does not achieve the target goal (I guess) which is having NuGet packages published with the .NET 10 target.
This PR should at least have changes to the following lines in the Directory.Build.props:

agent-framework/dotnet/Directory.Build.props

Lines 13 to 15 in 57ca139

	<ProjectsCoreTargetFrameworks>net9.0;net8.0</ProjectsCoreTargetFrameworks>
	<ProjectsDebugCoreTargetFrameworks>net9.0</ProjectsDebugCoreTargetFrameworks>
	<ProjectsTargetFrameworks>net9.0;net8.0;netstandard2.0;net472</ProjectsTargetFrameworks>

We should focus on taking Stephen's PR I've mentioned (#2128), because it does update all the packages, updates LangVersion, cleanups ifdefs and does many more other useful stuff, which should come all together IMO.

Maybe I am wrong, so not blocking the PR anyway

[javiercn]

I agree with @DeagleGross, I think we should go with #2128

[Youssef1313]

Yes, end goal would be #2128. But it doesn't harm to get this one merged until #2128 is finalized. This PR solely focuses on updating the .NET SDK, not the TFMs.

[stephentoub]

We should be able to merge #2128 once a build for Ignite is complete, if that hasn't happened already.

[crickman]

@Youssef1313 - @stephentoub is driving a comprehensive update that addresses this. I wonder if you'd be able to review and comment on this change: #2128