Spike: whiteboard collaboration service

[techsmyth]

Description

As a user I want that the connectivity to whiteboards is robust As a devops lead I want to be able to frequently update the server containers without disrupting collaboration on whiteboards

Acceptance criteria

• [ ] Separate "whiteboard-collaboration" service that is deployed in the cluster as a separate container
• [ ] Design for how this service interacts with the server for authorization + license checks (message bus approach?)

Spike: limit to 1.5 days? Or bigger + take further?

Additional Context

Screen shots / UX designs / data that are relevant.