Creating a Commerce ScaleUnit package for CommerceSDK via Developer Command Prompt for VS 2022 - login prompt??

[RethaLam]

I have used the Developer command prompt for VS for a long time. I used it for RetailSDK and when we switched over to CommerceSDK, I continue to use it. I'm currently running VS2022.
My steps are: Open the Developer command prompt as Administrator.
Then cd to the directory where I have the code to build the package.
Then first I run the following command to pull the latest nuget packages:
nuget restore e.g nuget restore commerce.sln

I created a commerce cloud scale unit package on October 15th 2024 without any issues.
Today I tried to run the above command and it suddenly ask me to log in with my work account and when I do, it tells me the account doesn't exist. Which is wrong, t does.
Before it prompts for the login, it tells me the file not found on
NotFound https://api.nuget.org/v3-flatcontainer/microsoft.dynamics.commerce.sdk.installers.scaleunit/index.json
And it complains it seems on the other nuget packages as well that the other projects use e.g. ScaleUnit.Installer, ScaleUnit, Knockout.js etc.

Some of the other errors:

Retrying 'FindPackagesByIdAsync' for source 'https://pkgs.dev.azure.com/commerce-partner/803bdde2-a918-4b56-806f-0f3b7546b1be/_packaging/aa42c2b9-2268-4106-9152-0108e4f0e843/nuget/v3/flat2/knockoutjs/index.json'.
The HTTP request to 'GET https://pkgs.dev.azure.com/commerce-partner/803bdde2-a918-4b56-806f-0f3b7546b1be/_packaging/aa42c2b9-2268-4106-9152-0108e4f0e843/nuget/v3/flat2/knockoutjs/index.json' has timed out after 100000ms.
GET https://pkgs.dev.azure.com/commerce-partner/803bdde2-a918-4b56-806f-0f3b7546b1be/_packaging/aa42c2b9-2268-4106-9152-0108e4f0e843/nuget/v3/flat2/knockoutjs/index.json
[CredentialProvider]DeviceFlow: https://pkgs.dev.azure.com/commerce-partner/Registry/_packaging/dynamics365-commerce/nuget/v3/index.json
[CredentialProvider]ATTENTION: User interaction required.

It times out because it doesn't want to accept my credentials.
So what is going on?

When I open the project in VS2022 , then it builds just fine.
I prefer to build my CloudScaleUnitExtensionPackage zip file using the Developer command prompt.

Note, that I have not even run the MSBuild command yet.
When I run the latter: msbuild /p:Configuration=Release -t:rebuild
It runs fine as usual. It still generates the error about the MSB4186 GetDirectoryName (logged with MSFT who logged it on gitHub issue #212). However, the latter doesn't prevent the creation of the CloudScaleUnit package zip-file.

Why suddenly this pop-up asking for my Microsoft account against VS2022 is registered as well as my access in LCS. So if VS2022 is working and I can log into LCS just fine, then this command shouldn't have a problem.