Improve the UX when source credentials can't be authenticated - Authentication Prompts do not indicate the Feed and Retry count etc

[nkolev92]

We try for a max of 3 times per source when a source can't be authenticated.

If you have many sources (and you don't have the rights), this could lead to getting 3 * sourceNumber prompts.

As part of this work we should also ensure that the errors are clearly communicated to the user (given that the prompts are not owned by NuGet.

[nkolev92]

Related to #1500

[aortiz-msft]

Still seeing reports about this in Developer Community

[prasethu]

Feedback from customer: https://developercommunity2.visualstudio.com/t/Version-1684-has-excessive-prompts-for/1332050

[zivkan]

related, or maybe this one is a duplicate: #7814

[prasethu]

The Visual Studio Connected Experience team gets a constant influx of these questions on our support alias heavily randomizing us. Can we get this prioritized soon?

[erdembayar]

Yet another VS experience feedback dup of this.

[nkolev92]

Another feedback ticket: https://developercommunity.visualstudio.com/t/This-version-of-VS-2022-repeatedly-asks-/1534482

[donnie-msft]

Another feedback ticket: https://developercommunity.visualstudio.com/t/Restoring-Nuget-packages-from-Azure-Dev-/1555305

[aortiz-msft]

One more FeedbackTicket: FeedbackTicket 1430698: "Sign in to your account" popup every time I build

[nkolev92]

cc @kartheekp-ms

[pilcherd]

Just experienced what was likely this today with Visual Studio 2022. We have a private VSO feed and when you open a project checked out in Visual Studio that references the private VSO feed, but the user does not have permissions to access the feed, we got infinite login requests with no detail or cause. Killing VS was the only out.

Guessed that the project nuget restore might be the cause. Added Reader permission to the VSO artifact feed and the login prompt went away.

Since all Visual Studio bug reports lead here, I am assuming this is a nuget issue.