chore(deps): update dotnet monorepo

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence	Type	Update
System.Text.Json (source)	6.0.8 -> 6.0.9					nuget	patch
dotnet-sdk	6.0.416 -> 6.0.417					dotnet-sdk	patch
mcr.microsoft.com/dotnet/runtime-deps	8b045ea -> 7f21c28					stage	digest

---

Release Notes

dotnet/runtime (System.Text.Json)

v6.0.9: .NET 6.0.9

Release

dotnet/sdk (dotnet-sdk)

v6.0.417: .NET 6.0.25

Compare Source

Release

---

Configuration

📅 Schedule: 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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

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

---

This PR has been generated by Mend Renovate. View repository job log here.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (2bd065b) 74.8% compared to head (37a10c0) 74.8%.

Additional details and impacted files

@@          Coverage Diff          @@
##            main    #892   +/-   ##
=====================================
  Coverage   74.8%   74.8%           
=====================================
  Files        235     235           
  Lines       9937    9937           
  Branches     971     971           
=====================================
  Hits        7435    7435           
  Misses      2231    2231           
  Partials     271     271           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[github-actions]

👋 Hi! It looks like you modified some files in the Detectors folder.
You may need to bump the detector versions if any of the following scenarios apply:

• The detector detects more or fewer components than before
• The detector generates different parent/child graph relationships than before
• The detector generates different devDependencies values than before

If none of the above scenarios apply, feel free to ignore this comment 🙂