chore(deps): update dependency polyfill to 10.6.0

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
Polyfill	nuget	minor	10.5.1 → 10.6.0

---

Release Notes

SimonCropp/Polyfill (Polyfill)

v10.6.0

Compare Source

• #​547 Add .NET 11 Process APIs
• #​548 Add dictionary/hash set get alternate lookup polyfill (o(n))
• #​549 Add string builder move chunks

---

Configuration

📅 Schedule: (UTC)

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

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

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

---

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

---

This PR has been generated by Mend Renovate.

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

_{NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.}

[claude]

Code Review

This is a straightforward Renovate-generated dependency bump: Polyfill 10.5.1 → 10.6.0 (minor version update).

Change: Single-line version string update in TUnit.Core/TUnit.Core.targets.

What's new in 10.6.0

• Add .NET 11 Process APIs
• Add dictionary/hash set get alternate lookup polyfill (O(n))
• Add string builder move chunks

Assessment: ✅ Approved

No concerns here. This is a minor version bump to a well-maintained polyfill library used to support downlevel target frameworks (netstandard2.0/2.1 and .NETFramework). The update adds new polyfills that TUnit doesn't necessarily use, but having them available is harmless.

The pinned version pattern in TUnit.Core.targets (rather than a floating range) is the right approach — it ensures reproducible builds and keeps downlevel consumers from picking up unexpected versions independently of TUnit's release cycle.