Resolve login when repr-ing AuthenticatedUser

[xmo-odoo]

It's extremely confusing to dump an AuthenticatedUser and get AuthenticatedUser(login=None) even though the AuthenticatedUser is correctly set up, and necessarily has a login.

This risks incurring additional requests, but I think in the contexts where it would be used (mostly at the shell or when debugging services) it's more helpful to actually show the information.

[EnricoMi]

I understand the confusion. But this project favours no unwanted REST calls. This change would cause a request for everyone else using this project, and there would be no way to not have the REST call in this situation.

I think you can easily call update() before printing the user or print user.login to get the desired behaviour.

[xmo-odoo]

Then maybe the repr for AuthenticatedUser when no call has been made say something like unknown / unresolved login?

Obviously it's easy to trigger the resolution when you know that's what the issue is, but when you don't and you assume the repr is the actual thing you start trying to debug why your user does not have a login and where that got lost.