chore(deps): update microsoft.testing to 2.2.2

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
Microsoft.Testing.Extensions.CrashDump	nuget	patch	2.2.1 → 2.2.2
Microsoft.Testing.Extensions.HangDump	nuget	patch	2.2.1 → 2.2.2
Microsoft.Testing.Extensions.Telemetry	nuget	patch	2.2.1 → 2.2.2
Microsoft.Testing.Extensions.TrxReport	nuget	patch	2.2.1 → 2.2.2
Microsoft.Testing.Extensions.TrxReport.Abstractions	nuget	patch	2.2.1 → 2.2.2
Microsoft.Testing.Platform	nuget	patch	2.2.1 → 2.2.2
Microsoft.Testing.Platform.MSBuild	nuget	patch	2.2.1 → 2.2.2

---

Release Notes

microsoft/testfx (Microsoft.Testing.Extensions.CrashDump)

v2.2.2

See release notes here.

---

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 these updates again.

---

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

---

This PR has been generated by Mend Renovate.

[claude]

Code Review: Dependency Update — Microsoft.Testing 2.2.1 → 2.2.2

This is a routine Renovate-bot patch bump for the entire Microsoft.Testing suite (7 packages in lock-step). The change is minimal and well-structured:

What changed:

• Directory.Packages.props: 6 centrally-managed package versions updated from 2.2.1 → 2.2.2
• examples/CloudShop/CloudShop.Tests/CloudShop.Tests.csproj: 1 directly-pinned version updated to match

Observations:

The CloudShop.Tests.csproj still pins Microsoft.Testing.Platform.MSBuild directly at a specific version instead of relying on the central Directory.Packages.props entry. This is a minor inconsistency — since this project is within the repo, it could inherit the version centrally managed in Directory.Packages.props and be updated in one place in future bumps. Not a blocker for this PR, but worth a cleanup pass.

Everything else looks correct. All 7 packages are bumped consistently to the same patch version, which is expected for the Microsoft.Testing family (they version together). No API surface changes are expected from a patch release.

✅ Approved. Safe to merge.

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Metrics 0 complexity

Metric	Results
Complexity	0

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.}