Automatic Vault Lock Forces Workspace Change

### Steps To Reproduce

1. Open Bitwarden in any workspace (we'll say workspace 1).
2. Set a vault timeout (Edit > Settings > Security > Vault Timeout). Mine is set for 2 minutes.
3. Open a browser on workspace 2 and go to a website that requires username and password saved in your vault.
4. Copy and paste login credentials from Bitwarden, and begin doing whatever you need to do on said website.

### Expected Result

Bitwarden locks my vault after 2 minutes.

### Actual Result

Bitwarden does lock my vault after 2 minutes. _However,_ when it locks, it automatically forces my screen back to workspace 1.

### Screenshots or Videos

_No response_

### Additional Context

I'm unsure if this is actually a Bitwarden problem. This behavior is new, but that doesn't necessarily mean that it's from an update to Bitwarden. My first thought was that it's either a Bitwarden problem or a problem with my window manager (kwin). From what I've been able to determine so far, it doesn't seem to be a kwin problem, but I'm still investigating. Perhaps this is neither a Bitwarden nor a kwin problem, but at this time I believe Bitwarden to be the most likely culprit. I don't know if it would be from upstream Bitwarden or if it has something to do with how the Arch Linux devs packaged the binary in their repos. I'll be looking into this as well.

### Operating System

Linux

### Operating System Version

Arch Linux using Linux 6.10.9-arch1-2 kernel.

### Installation method

Other

### Build Version

Version 2024.8.1 Shell 31.6.0 Renderer 126.0.6478.234 Node 20.17.0 Architecture x64

### Issue Tracking Info

- [X] I understand that work is tracked outside of GitHub. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.