Update dotnet monorepo to v10

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
Microsoft.AspNetCore.Components.WebAssembly (source)	8.0.24 → 10.0.9
Microsoft.AspNetCore.Components.WebAssembly.DevServer (source)	8.0.24 → 10.0.9
Microsoft.AspNetCore.Components.WebAssembly.Server (source)	8.0.24 → 10.0.9
Microsoft.AspNetCore.TestHost (source)	8.0.24 → 10.0.9
Microsoft.Extensions.Configuration.CommandLine (source)	8.0.0 → 10.0.9
Microsoft.Extensions.Configuration.EnvironmentVariables (source)	8.0.0 → 10.0.9
Microsoft.Extensions.Configuration.UserSecrets (source)	8.0.1 → 10.0.9
System.Collections.Immutable (source)	9.0.0 → 10.0.9
System.Text.Json (source)	9.0.9 → 10.0.9

---

Release Notes

dotnet/dotnet (Microsoft.AspNetCore.Components.WebAssembly)

v10.0.9

v10.0.8

v10.0.7

v10.0.6

v10.0.5

v10.0.4

v10.0.3

v10.0.2

v10.0.1

v9.0.7: .NET 9.0.7

You can build .NET 9.0 from the repository by cloning the release tag v9.0.7 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

v9.0.6: .NET 9.0.6

You can build .NET 9.0 from the repository by cloning the release tag v9.0.6 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

v9.0.5: .NET 9.0.5

You can build .NET 9.0 from the repository by cloning the release tag v9.0.5 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

v9.0.4: .NET 9.0.4

You can build .NET 9.0 from the repository by cloning the release tag v9.0.4 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

v9.0.3: .NET 9.0.3

You can build .NET 9.0 from the repository by cloning the release tag v9.0.3 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

v9.0.2: .NET 9.0.2

You can build .NET 9.0 from the repository by cloning the release tag v9.0.2 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

v9.0.1: .NET 9.0.1

You can build .NET 9.0 from the repository by cloning the release tag v9.0.1 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

v9.0.0: .NET 9.0.0

You can build .NET 9.0 from the repository by cloning the release tag v9.0.0 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

AI Reviewer: first review requested successfully. AI can make mistakes. Always validate suggestions.

_{TIP This summary will be updated as you push new changes.}

[codacy-production]

Pull Request Overview

While the Codacy analysis indicates the PR is up to standards, there is a critical compatibility risk that should be addressed before merging. The PR updates dependencies to version 10.0.9, yet these definitions remain within an ItemGroup conditioned for 'net8.0'. Major version jumps in .NET packages typically require a corresponding update to the Target Framework Moniker (TFM). Using .NET 10 packages in a .NET 8 environment may lead to build failures or runtime dependency issues. Furthermore, the central package management file contains duplicate entries for several Microsoft.AspNetCore packages that should be consolidated to prevent configuration drift.

About this PR

• There is a high-risk mismatch between the packages and the environment. .NET 10 packages are being introduced into a 'net8.0' scope. Ensure the project is ready to move to the .NET 10 SDK and runtime, or verify if these specific packages offer backward compatibility with .NET 8.

Test suggestions

• Verify successful compilation and runtime compatibility of the application when targeting .NET 8 while using .NET 10 packages.

Prompt proposal for missing tests

Consider implementing these tests if applicable:
1. Verify successful compilation and runtime compatibility of the application when targeting .NET 8 while using .NET 10 packages.

_{TIP Improve review quality by adding custom instructions
TIP How was this review? Give us feedback}

[codacy-production]

_{🔴 HIGH RISK}

Updating dependencies to v10.0.9 while the TargetFramework is set to 'net8.0' (as per the condition on line 3) is a major risk. .NET 10 packages usually require the .NET 10 SDK and runtime. Verify if these packages explicitly support .NET 8 or if the project TFM should also be updated.

[codacy-production]

_{⚪ LOW RISK}

Suggestion: Remove these redundant package version declarations. They are already defined earlier in the same ItemGroup (lines 4-7). Maintaining duplicate entries increases the risk of version mismatch if future updates are only applied to one set.

[github-actions]

Test Results

0 tests  ±0   0 ✅ ±0   0s ⏱️ ±0s
0 suites ±0   0 💤 ±0 
0 files   ±0   0 ❌ ±0 

Results for commit 434145b. ± Comparison against base commit c15f555.

♻️ This comment has been updated with latest results.