If a release loading results in Picard asking for authentication, the authentication is started and then cancelled, the release loading gets stuck in "loading album information state".

To reproduce:

1. Configure Picard to require authentication on release loading (e.g. enable user tags or ratings)
2. Be logged out
3. Load any release into Picard
4. When Picard shows the "authentication required dialog", click yes
5. In the browser oauth login screen, click cancel

Result:

• The browser navigates to http://127.0.0.1:8002/auth?error=access_denied&state=xxx
• Picard web server shows an error "Missing parameter "code"."
• The release loading is stuck in "loading album information"
• Reloading is not possible, log shows "Not reloading, some requests are still active."
• Removing the release and loading again does also not work, the login dialog won't show up again and loading is immediatelly stuck