Resolve issues with dotnet-openapi tests in latest SDK

[captainsafia]

Following the latest SDK bump in #32581, the dotnet-openapi tests are failing due to some issues with the new workload resolution flag.

  Error Message:
   Threw error: The SDK 'Microsoft.NET.SDK.WorkloadAutoImportPropsLocator' specified could not be found.  /Users/captainsafia/github.com/dotnet/aspnetcore/.dotnet/sdk/6.0.100-preview.5.21264.3/Sdks/Microsoft.NET.Sdk/targets/Microsoft.NET.Sdk.ImportWorkloads.props

Expected: True
Actual:   False
  Stack Trace:
     at Microsoft.DotNet.OpenApi.Tests.OpenApiTestBase.AssertNoErrors(Int32 appExitCode) in /Users/captainsafia/github.com/dotnet/aspnetcore/src/Tools/Microsoft.dotnet-openapi/test/OpenApiTestBase.cs:line 116
   at Microsoft.DotNet.OpenApi.Add.Tests.OpenApiAddURLTests.OpenApi_Add_Url() in /Users/captainsafia/github.com/dotnet/aspnetcore/src/Tools/Microsoft.dotnet-openapi/test/OpenApiAddURLTests.cs:line 158
--- End of stack trace from previous location ---

And when run locally:

❯ ~/github.com/dotnet/aspnetcore/.dotnet/dotnet ~/github.com/dotnet/aspnetcore/artifacts/bin/Microsoft.dotnet-openapi/Debug/net6.0/dotnet-openapi.dll add url "https://google.com"
Downloading to '/Users/captainsafia/github.com/dotnet/aspnetcore/src/Tools/Microsoft.dotnet-openapi/test/google.json'.

The SDK 'Microsoft.DotNet.Arcade.Sdk' specified could not be found.  /Users/captainsafia/github.com/dotnet/aspnetcore/Directory.Build.props

Skipping the tests for now to unblock our build issues but we'll need to follow-up on this once we have a resolution in the SDK.

Ref: dotnet/sdk#17461

Thanks for contacting us.

We're moving this issue to the Next sprint planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

[dougbu]

I'm pretty sure there's nothing to "resolve" here. Testing in #36171

[captainsafia]

@dougbu A subsequent SDK update probably resolved the issue. As I recall, this particular stacktrace was tracked down to an external issue.