TaskAnalyzer: report MT diagnostics as suggestions for non-MT tasks

[VolPlita]

Problem

MT-related TaskAnalyzer diagnostics can also provide useful migration guidance for non-MT tasks. However, reporting them as warnings or errors for those tasks can disrupt builds that are not adopting multithreaded task execution.

Non-MT tasks should still receive the selected diagnostics, but only as suggestions or informational messages. MT-scoped tasks need stronger enforcement because unsafe behavior can affect other tasks running in the shared process.

Proposed behavior

For selected MT-related diagnostics:

• Report them as Suggestion/Info for non-MT tasks, so migration guidance remains visible in the IDE without normally affecting command-line builds.
• Report the same diagnostic IDs at their intended Warning or Error severity for MT-scoped tasks.
• Always let an explicit dotnet_diagnostic.<ID>.severity setting in .editorconfig or .globalconfig override the analyzer's contextual default.

This should apply only to diagnostics that the team wants to enforce strongly for MT tasks. Disabled and advisory rules must retain their intended defaults.

Scope and implementation

This issue covers two parts of the same change:

1. Behavior: report selected MT-related diagnostics as Suggestion/Info for non-MT tasks while retaining Warning/Error enforcement for MT-scoped tasks.
2. Implementation: add contextual severity to TaskAnalyzer so it can select the appropriate default severity from the task context while preserving the same diagnostic ID and standard analyzer configuration.

Contextual severity is the mechanism required to implement the behavior, not a separate independent feature. The implementation must verify that an explicit dotnet_diagnostic.<ID>.severity setting overrides the contextual default for both MT and non-MT tasks.

Design questions

• Which diagnostic IDs should use contextual severity?
• How should this behavior interact with msbuild_task_analyzer.run_mt_analyzers_on_all_tasks from Scope MT-specific TaskAnalyzer diagnostics and support .editorconfig #14775?

Related: #14775, #14990

[VolPlita]

My proposal is to apply contextual severity to MSBuildTask0002, MSBuildTask0003, and MSBuildTask0005 only when it represents a transitive MSBuildTask0002/0003 violation. These would be Info/Suggestion for non-MT tasks and retain their current Warning severity for MT-scoped tasks. Other diagnostic IDs should keep their existing behavior unless we make a separate explicit decision about them.

[VolPlita]

My proposal is:

• When run_mt_analyzers_on_all_tasks is missing or false, report the selected diagnostics as Info/Suggestion for non-MT tasks and at their normal Warning severity for MT-scoped tasks.
• When it is true, use the normal Warning severity for all tasks.
• An explicit dotnet_diagnostic.<ID>.severity setting should override both behaviors.

This preserves the existing option as the opt-in for full MT-analyzer enforcement on all tasks while still providing quiet migration guidance by default.