Treat typed task diagnostics as suggestions

[OvesN]

Summary

Adds MSBuildTask0006-MSBuildTask0008 to the existing report-only analyzer configuration, unblocking dotnet/dotnet#8367.

Testing

Verified WarnAsError fails without the overrides and succeeds under both SDK editorconfig scopes.

[azure-pipelines]

Azure Pipelines:
Successfully started running 1 pipeline(s).
2 pipeline(s) were filtered out due to trigger conditions.
There may be pipelines that require an authorized user to comment /azp run to run.

[azure-pipelines]

Azure Pipelines:
Successfully started running 1 pipeline(s).
2 pipeline(s) were filtered out due to trigger conditions.
There may be pipelines that require an authorized user to comment /azp run to run.

[Copilot]

Pull request overview

Updates the repository’s “report-only onboarding” configuration for Microsoft.Build.TaskAuthoring.Analyzer so the newer typed-task diagnostics (MSBuildTask0006–MSBuildTask0008) are also treated as suggestions, preventing warn-as-error builds from failing while the multithreaded task migration is still in progress.

Changes:

• Downgrade MSBuildTask0006–MSBuildTask0008 to suggestion in the repo-root .editorconfig.
• Mirror the same severity overrides in src/StaticWebAssetsSdk/.editorconfig (which has root = true and doesn’t inherit from the repo root).
• Update onboarding documentation text in eng/MSBuildTaskAuthoringAnalyzer.props to reflect the expanded rule range.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.

File	Description
.editorconfig	Extends the report-only severity downgrades to include MSBuildTask0006–MSBuildTask0008.
src/StaticWebAssetsSdk/.editorconfig	Keeps the StaticWebAssetsSdk local root config in sync with the repo-root analyzer severity overrides.
eng/MSBuildTaskAuthoringAnalyzer.props	Updates the explanatory comment to reflect MSBuildTask0001–MSBuildTask0008 onboarding.

[baronfel]

Why WarningsNotAsErrors and not the roslyn diagnostics configuration in editorconfig? I would expect most analyzer users to use this mechanism.

[OvesN]

Why WarningsNotAsErrors and not the roslyn diagnostics configuration in editorconfig? I would expect most analyzer users to use this mechanism.

@baronfel I think you mean the first commit, I moved the configuration to editorconfig later.

[baronfel]

@OvesN you are right - when I was reading the issue (and not looking at the code) I inferred that WarningsNotAsErrors was being used, but I see you're using editorconfig. All good!

[rainersigwald]

/backport to release/11.0.1xx

[github-actions]

Started backporting to release/11.0.1xx (link to workflow run)