Follow up: Bitbucket Forge migration issue

I’m having an issue after upgrading to Forge. I’m not sure if it’s a Bitbucket problem or a Sonar problem. I have my own Bitbucket account, but we also have a delegate “system” user in Bitbucket that runs the pipelines. I sometimes have to log in to Bitbucket as the system user to update tokens. After switching SonarQube Cloud to Forge in Bitbucket workspace, when I log in to Sonar using the Bitbucket option, I get logged in to Sonar with the system account, which didn’t have access to anything in Sonar, even though I was logged in to Bitbucket with my real account, and there is no way to switch Sonar to another account. I eventually managed to log into Sonar with the correct account by opening Bitbucket in an incognito window, clicking the link in the Sonar repo header, and then I was able to add the system user to the owners group so that when I land in Sonar with the system account I am still able to perform my tasks, but it’s annoying. How do I reset the Bitbucket - Sonar connection in a regular browser session without having to always use an incognito?