Hanling user "logged in" state in a more robust way in login_info

[marcus-oscarsson]

The request to login_info raised an exception and incorrectly returned a stack trace with the 200 status code.

The handling within login_info is perhaps still not ideal but this PR makes sure that the is_anonymous on current_user is updated correctly before the code that returns the user information is called. The "event" of "no valid sessions" should probably not be seen as an exception.

All requests raising an exceptions now returns a 501 without the traceback

Fixes #1477

[axelboc]

Fixes #1477 probably? (I've opened a ticket with our IT division about the conflicting timezone on Ubuntu 24.)

[marcus-oscarsson]

:), thanks thats great because @walesch-yan also had the issue. I'm not sure it fixes the actual issue but you wont get it right away, I guess you would bump into the timezone issue at some point in anyways.