Update mstest monorepo to v4 (major)

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
MSTest.Analyzers	3.11.0 -> 4.0.1
MSTest.TestAdapter	3.11.0 -> 4.0.1
MSTest.TestFramework	3.11.0 -> 4.0.1

---

Release Notes

microsoft/testfx (MSTest.Analyzers)

v4.0.1

See the release notes here

v4.0.0

What is new?

Assert.That

MSTest v4 adds a new type of assertion, that allows you to write any expression, and it will inspect the result to give you more information on failure. Providing a very flexible way to assert complicated expressions. Here a simple example:

[TestClass]
public sealed class Test1
{
    [TestMethod]
    public void TestMethod1()
    {
        var animal = "Tiger";
        var zoo = new Zoo();
        Assert.That(() => zoo.GetAnimal() == animal);
    }
}

public class Zoo
{
    public string GetAnimal()
    {
        return "Giraffe";
    }
}

Assert.That(() => zoo.GetAnimal() == animal) failed.
Details:
    animal = "Tiger"     
    zoo.GetAnimal() = "Giraffe"

CallerArgumentExpression

CallerArgumentExpression is consumed by all assertions, to make them aware of the expressions used in the assertion. In the example below, we now know what both the expected and actual values are. But also what value they come from, giving us opportunity to provide better error messages:

[TestClass]
public sealed class Test1
{
    [TestMethod]
    public void TestMethod1()
    {
        string animal = null;
        Assert.AreEqual("Giraffe", animal);
    }
}

Error Message: Assert.AreEqual failed. Expected:<Giraffe>. Actual:<>. 
'expected' expression: '"Giraffe"', 'actual' expression: 'animal'.

Breaking changes

We hidden many types that should have never been public in the first place. We believe that most of the changes won't have any real user impact. For the changes where we expect user impact migration guide from v3 is provided: https://learn.microsoft.com/dotnet/core/testing/unit-testing-mstest-migration-v3-v4

See the MSTest changelog here: https://github.com/microsoft/testfx/blob/main/docs/Changelog.md#4.0.0
See the Microsoft.Testing.Platform changelog here: https://github.com/microsoft/testfx/blob/main/docs/Changelog-Platform.md#2.0.0

Full changelog here: microsoft/testfx@v3.11.0...v4.0.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 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.

[codecov]

Codecov Report

❌ Patch coverage is 76.66667% with 7 lines in your changes missing coverage. Please review.
✅ Project coverage is 89.6%. Comparing base (eddc8b7) to head (32f7c1e).
⚠️ Report is 2 commits behind head on main.

Files with missing lines	Patch %	Lines
...Utilities/Attributes/SkipTestOnWindowsAttribute.cs	60.0%	4 Missing ⚠️
...lities/Attributes/SkipTestIfNotWindowsAttribute.cs	70.0%	3 Missing ⚠️

Additional details and impacted files

@@           Coverage Diff           @@
##            main   #1512     +/-   ##
=======================================
- Coverage   90.3%   89.6%   -0.8%     
=======================================
  Files        418     418             
  Lines      35275   35292     +17     
  Branches    2188    2193      +5     
=======================================
- Hits       31881   31622    -259     
- Misses      2951    3232    +281     
+ Partials     443     438      -5     

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

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.