In order to not complicate VS Code API, the initial design of dynamic auth providers was to register one per auth server/resource server pair.

> note resource server is the same as mcp server more-or-less

that's why the auth provider id was a combo of those two urls.

However, after registration, when we wanted to see what auth provider an mcp server would use, we'd only look at the auth server uri... this caused a bug where the same auth provider was being re-used for multiple mcp servers, even though those are 2 different resources.

The fix? When fetching what auth provider to use, also pass in the resource server and look at the resource server on the auth provider to see if they match.

I still think we need an larger re-design to allow auth providers to take in `resource`s ...but this addresses the issue for now. We will need to do this once Entra supports `resource` which should happen in the new year ..,,..... maybe

Fixes https://github.com/microsoft/vscode/issues/272047