Failing test `Nunit_PerTestFrameworkTemplatesTests.TemplatesForIndividualTestFrameworks`

[radical]

Failing build with:

WebTests.cs(10,23): error VSTHRD200: Use "Async" suffix in names of methods that return an awaitable type (https://github.com/Microsoft/vs-threading/blob/main/doc/analyzers/VSTHRD200.md)

This broke in #7869 and slipped through because we don't run template tests for PR validation.
cc @DamianEdwards @joperezr @eerhardt

EDIT:
Also,
Aspire.Workload.Tests.BuildAndRunTemplateTests.BuildAndRunStarterTemplateBuiltInTest: \WebTests.cs(10,23): error VSTHRD200: Use "Async" suffix in names of methods that return an awaitable type (https://github.com/Microsoft/vs-threading/blob/main/doc/analyzers/VSTHRD200.md)

.. and Aspire.Workload.Tests.Nunit_PerTestFrameworkTemplatesTests.TemplatesForIndividualTestFrameworks: IntegrationTest1.cs(19,24): error VSTHRD200: Use "Async" suffix in names of methods that return an awaitable type (https://github.com/Microsoft/vs-threading/blob/main/doc/analyzers/VSTHRD200.md

[danmoseley]

You scratched that out? Apparently we build templates in official build, maybe that's enough.

I"ll fix since I'm there.

[radical]

You scratched that out?

Yeah, I was trying to check why it is being hit now because the particular lines in the error didn't change in that commit. But also it started failing after that one. Did we update the sdk being used, or have new analyzers?

[radical]

Apparently we build templates in official build, maybe that's enough.

It wouldn't have been caught there because only the Workload(template) tests create projects from the templates.

[radical]

@danmoseley since you are fixing this, fyi, I have updated the description with two more cases of the same thing but in other templates.

[danmoseley]

#8012

I just searched for async Task .*(?<!Async)\( .. I don't know why but VS doesn't give this error when I opened a project created from the templates

[eerhardt]

This failed from #7991. I reverted that change with #7999. You can read why it broke in the revert PR description.

[radical]

This failed from #7991. I reverted that change with #7999. You can read why it broke in the revert PR description.

Ah.. should we close this, and the corresponding PR then?

[eerhardt]

Ah.. should we close this, and the corresponding PR then?

Yes, I believe so.

[mitchdenny]

Tjese tests