fix: For installing from a lock file without doing a solve beforehand

[tdejager]

Because of caching, the credentials were not available when a solve was
skipped. This makes sure the username and potentially password are
available for pulling from the registry.

More details are in this issue: #1374 (comment)

[ruben-arts]

Nice find, how hard would it be to create a test for this?

[tdejager]

Nice find, how hard would it be to create a test for this

First you need an external private registry if you want to rely on our own gcp instance being up,otherwise you need a proxy for pypi or something.
Second, a way to programatically clear the cache or ignore it?
Finally, a way to delete the .pixi folder.

I think that would be enough.

[ruben-arts]

Do you think it's worth adding it now?

[tdejager]

Do you think it's worth adding it now?

I'll try and make it :)

[tdejager]

I'm thinking now it's somewhat hard to make a test because I need a global installation of keyring. This would make the test only runnable from a pixi env (with keyring) or when globally installed. So a cargo t without the global keyring installation would fail. At this point, I don't really think that's worth it for now :) wdyt @ruben-arts ?

[tdejager]

Verification that it works for azure: #1374 (comment)