feat: ws for updating vote count and active connections

[edalholt]

Closes #159

Using WebSockets for updating vote count and active participants in real-time.

When researching this issue I also noticed the basic plan in Azure is restricted to 350 concurrent connections.
For production the standard plan is therefore recommend.
https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/azure-subscription-service-limits

Live count updated for every logged in organizer:

[Xtrah]

I have come to think of NTNUI/vote and NTNUI/opptak and regular pull requests. Perhaps we should remove the approval for PRs to dev (and maybe just commit directly) in these projects, and do a proper review from dev to main?

[edalholt]

Maybe, I am going to set up the production environment for vote soon, so we can consider it then. I also think it will be more difficult to understand what you are approving when it's consisting of 3-4+ pull requests

I have come to think of NTNUI/vote and NTNUI/opptak and regular pull requests. Perhaps we should remove the approval for PRs to dev (and maybe just commit directly) in these projects, and do a proper review from dev to main?

[Xtrah]

Jumping between projects to review, I think it's a somewhat challenging already to understand what the different conventions are for each project. We should consider including a How to test in PR templates/descriptions, such as this one 😺

[LiviaValenti]

Super system 🤩 Nice job! Will test in dev as agreed upon 🤝