Disable roll-forward to fix spontaneous CI build failure.

[Arlodotexe]

See https://github.com/CommunityToolkit/Windows/actions/runs/21039291527/job/60496336547

Error observed is:

     6>CSC : error CS8032: An instance of analyzer Microsoft.CodeAnalysis.UseExplicitTupleName.UseExplicitTupleNameDiagnosticAnalyzer cannot be created from C:\Program Files\dotnet\sdk\9.0.309\Sdks\Microsoft.NET.Sdk\codestyle\cs\Microsoft.CodeAnalysis.CodeStyle.dll : Exception has been thrown by the target of an invocation.. [D:\a\Labs-Windows\Labs-Windows\tooling\CommunityToolkit.Tooling.TestGen\CommunityToolkit.Tooling.TestGen.csproj]

Fixes

PR Type

What kind of change does this PR introduce?

What is the current behavior?

What is the new behavior?

PR Checklist

Please check if your PR fulfills the following requirements:

• Created a feature/dev branch in your fork (vs. submitting directly from a commit on main)
• Based off latest main branch of toolkit
• Tested code with current supported SDKs
• New component
  • Documentation has been added
  • Sample in sample app has been added
  • Analyzers are passing for documentation and samples
  • Icon has been created (if new sample) following the Thumbnail Style Guide and templates
• Tests for the changes have been added (if applicable)
• Header has been added to all new source files
• Contains NO breaking changes

Other information

[Arlodotexe]

See also

• Disable roll-forward to fix spontaneous CI build failure. Labs-Windows#775
• Disable roll-forward to fix spontaneous CI build failure. Tooling-Windows-Submodule#302

[michael-hawker]

From other PR linking to the underlying Roslyn issue here: dotnet/roslyn#82010