chore(deps): update dependency microsoft.net.test.sdk to v17.9.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
Microsoft.NET.Test.Sdk	17.8.0 -> 17.9.0

---

Release Notes

microsoft/vstest (Microsoft.NET.Test.Sdk)

v17.9.0

What's Changed

• Remove dependency on Nuget.Frameworks by @​nohwnd in https://github.com/microsoft/vstest/pull/4693
• Add platform guard by @​dotMorten in https://github.com/microsoft/vstest/pull/4737
• Remove javascript in HtmlLogger by @​daveMueller in https://github.com/microsoft/vstest/pull/4744
• Fix CPU is consumed by polling frequently when there is no subscriber by @​nohwnd in https://github.com/microsoft/vstest/pull/4735
• Create a proper MSBuild ToolTask based VSTestTask by @​mcartoixa in https://github.com/microsoft/vstest/pull/2702
• Update SDK, copy logger by @​nohwnd in https://github.com/microsoft/vstest/pull/4755
• Fix staircase in logger by @​nohwnd in https://github.com/microsoft/vstest/pull/4756
• Update dump client to latest by @​nohwnd in https://github.com/microsoft/vstest/pull/4724
• [rel/17.9] Disable testhost prestart by @​nohwnd in https://github.com/microsoft/vstest/pull/4836

New Contributors

• @​jithu7432 made their first contribution in https://github.com/microsoft/vstest/pull/4698
• @​mcartoixa made their first contribution in https://github.com/microsoft/vstest/pull/2702

Full Changelog: microsoft/vstest@v17.8.0...v17.9.0

---

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.

🔕 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. View repository job log here.

[github-actions]

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.