Allow AssemblyCleanup/ClassCleanup to have TestContext parameter

[Youssef1313]

Fixes #4233

TODOs:

• Add tests
• Update analyzers and add analyzer tests

Copilot reviewed 5 out of 9 changed files in this pull request and generated 2 comments.

Files not reviewed (4)

• src/Adapter/MSTestAdapter.PlatformServices/PublicAPI/PublicAPI.Unshipped.txt: Language not supported
• src/Adapter/MSTest.TestAdapter/Execution/ClassCleanupManager.cs: Evaluated as low risk
• src/Adapter/MSTest.TestAdapter/Execution/TestAssemblyInfo.cs: Evaluated as low risk
• src/Adapter/MSTest.TestAdapter/Execution/TestExecutionManager.cs: Evaluated as low risk

Comments suppressed due to low confidence (3)

src/Adapter/MSTest.TestAdapter/Execution/TestClassInfo.cs:494

• Passing null! for TestContext can lead to a NullReferenceException if the method expects a TestContext parameter. Ensure a valid TestContext is passed.

ClassCleanupException = classCleanupMethod is not null ? InvokeCleanupMethod(classCleanupMethod, BaseClassCleanupMethods.Count, null!) : null;

src/Adapter/MSTest.TestAdapter/Execution/TestClassInfo.cs:499

• Passing null! for TestContext can lead to a NullReferenceException if the method expects a TestContext parameter. Ensure a valid TestContext is passed.

ClassCleanupException = InvokeCleanupMethod(classCleanupMethod, baseClassCleanupQueue.Count, null!);

src/Adapter/MSTest.TestAdapter/Execution/UnitTestRunner.cs:367

• The new ForceCleanup method signature should be covered by tests to ensure that the sourceLevelParameters and logger are correctly passed and utilized.

internal void ForceCleanup(IDictionary<string, object?> sourceLevelParameters, IMessageLogger logger) => ClassCleanupManager.ForceCleanup(_typeCache, sourceLevelParameters, logger);