Per: https://issues.jenkins.io/browse/JENKINS-60200

Sometimes the 1-hour cache of teams and organizations can cause issues. In particular, it causes problems when you have SSO turned on for an organization and the person logging in needs to remember to authorize SSO for a given organization and forgets.

The user story is this:
I log into a Jenkins with team-level permissions in my SSO enabled organization. I see this screen:

and I forget to click the Authorize button. I then get permission denied. I then click logout to try and fix that, but when I come back in after authorizing my organization; I still get permission denied because of the cache.

This PR invalidate the cache on fresh logins. This both solves the reported issue, and allows a user to have an active way to refresh their personal cache of teams and organizations by logging out and logging in while leaving caching in place for token flows and session accesses for performance and to minimize GitHub API calls.

Notes: I didn't see a logout hook in the Security Realm or I'd prefer to clear the caches there instead of during the fresh OAuth flow. If someone with more expertise knows how to hook there, I'm happy to move the user cache clearing to that hook.

• Make sure you are opening from a topic/feature/bugfix branch (right side) and not your main branch!
• Ensure that the pull request title represents the desired changelog entry
• Please describe what you did
• Link to relevant issues in GitHub or Jira
• Link to relevant pull requests, esp. upstream and downstream changes
• Ensure you have provided tests - that demonstrates feature works or fixes the issue