Docs - Publishing with missing project file on Windows fails to return MSB1003 or useful error if multiple .NET SDKs are installed.

From within a windows terminal, running spacetime publish foo when the working directory does not contain a project file, and the system has more than 1 .NET SDK version installed, the terminal will return an error message that does not provide the user a useful path forward.

Expected message ( As seen when only 1 .NET SDK version is installed):
MSBUILD : error MSB1003: Specify a project or solution file. The current working directory does not contain a project or solution file. Error: command ["dotnet", "publish", "-c", "Release", "-v", "quiet"] exited with code 1

Returned message:
Error: .NET SDK 8.0 is required, but found {version}. If you have multiple versions of .NET SDK installed, configure your project using https://learn.microsoft.com/en-us/dotnet/core/tools/global-json.

Notes:
Because no user projects are in the directory when the command is run, the error message returned does not provide the user a path forward to resolve the problem.

To check the versions of .NET SDKs installed on the current system, run the following in a PowerShell terminal:
dotnet --list-sdks

Start by reproducing spacetime publish foo from a Windows terminal in a directory without a project file, with multiple .NET SDKs installed, and compare it with the single-SDK output. Trace the publish command's error handling; done means the missing-project case returns MSB1003 or another useful path forward instead of only the SDK-version message.