interactive restore failing in latest net7 sdks

Describe the bug

dotnet restore --interactive fails to run the interactive tasks required to authenticate internal feeds msbuild /t:restore /p:nugetInteractive=true does seem to work as a workaround

To Reproduce

Add an internal feed to your nuget.config and try to get it to authenticate using dotnet restore --interactive

[marcpopMSFT]

I was reproducing it with the following steps

1. Installing the 6.0.401 candidate build from the artifacts tab
2. Running installcredprovider per these instructions
3. Adding the private feed to a nuget config file (dotnet new nugetconfig, dotnet nuget add source https://pkgs.dev.azure.com/dnceng/internal/_packaging/6.0.401-servicing.22421.13-shipping/nuget/v3/index.json)
4. Then dotnet new console
5. Then dotnet build -r win-x64 --interactive

Step 5 without the nuget config file should give an error NU1102 not able to find 6.0.9 versions of various runtime packages. Step 5 will give error NU1301 if --interactive is not working along with C:\Program Files\dotnet\sdk\7.0.100-rc.1.22431.12\NuGet.targets(132,5): warning : The plugin credential provider could not acquire credentials. Authentication may require manual action. Consider re-running the command with --interactive for dotnet, /p:NuGetInteractive="true" for MSBuild or removing the -NonInteractive switch forNuGet [C:\Users\WDAGUtilityAccount\test\bug.csproj]

Success will give you the following and an ask to log in the web browser. [NuGet Manager] [CredentialProvider]DeviceFlow: https://pkgs.dev.azure.com/dnceng/internal/_packaging/6.0.401-servicing.22421.13-shipping/nuget/v3/index.json [NuGet Manager] [CredentialProvider]ATTENTION: User interaction required.

[marcpopMSFT]

@rokonec @AR-May @MichalPavlik this appears to be caused by msbuild server. I had it succeed once for me after trying a bunch of times and on a hunch, I disabled msbuild server (using DOTNET_CLI_DO_NOT_USE_MSBUILD_SERVER) and it started working. Once I turned msbuild server back on, it worked the first time but every time after that failed.

Note that --interactive just passes -property:NuGetInteractive=true through to msbuild. Is one of you available to take a look? Thanks.