Make login procedure more resillient

[ShadowJonathan]

I got TFF that the user had an error inbetween these lines, where hasSuccessfulyConnectedToEndpoint would show a "successfully logged in" message, but getUserID failed, likely due to a network issue.

We should richen our paths where we act on the API, if we can differentiate here between a network issue, a server unavailability issue, and a true rejection, then we can make this process more resillient, even if it "takes a while".

This is a GET requests, those are reasonably idempotent, we should make it possible to automatically retry these, somehow.