Update WebSocket Notifications

[BlackDex]

Previously the websocket notifications were using the string app_id as the
ContextId. This was incorrect and should have been the device_uuid
from the client device executing the request. The clients will ignore
the websocket request if the uuid matches. This also fixes some issues
with the Desktop client which is able to modify attachments within the
same screen and causes an issue when saving the attachment afterwards.

Also changed the way to handle removed attachments, since that causes an
error saving the vault cipher afterwards, complaining about a missing
attachment. Bitwarden ignores this, and continues with the remaining
attachments (if any). This also fixes #2591 .

Further some more websocket notifications have been added to some other
functions which enhance the user experience.

• Logout users when deauthed, changed password, rotated keys
• Trigger OrgSyncKeys on user confirm and removal
• Added some extra to the send feature

Also renamed UpdateTypes to match Bitwarden naming.

[tessus]

The clients will ignore the websocket request if the uuid matches.

Hmm, aren't the websocket requests supposed to work for a specific device? Thus the device (client) should ignore the websocket request, if the uuid DOES NOT match.

Or am I missing something here?

[BlackDex]

The clients will ignore the websocket request if the uuid matches.

Hmm, aren't the websocket requests supposed to work for a specific device? Thus the device (client) should ignore the websocket request, if the uuid DOES NOT match.

Or am I missing something here?

All applicable clients will receive the exact same websocket notification. That includes the client which made the change. Because that client already has the correct changes it doesn't need to pull them in again. So the device id if the client which triggered the notification is sent with it, and then that specific client will ignore the request, all others will act upon the message and fetch the latest cipher data, or sync etc..

[tessus]

Ah, ok. For some reason I had the impression that some event had to be sent to a signle device, but yep, it's basically a broadcast. Thus I had it backwards. Makes sense.