refactoring: remove socket.io in favor of native Websocket

[peterpeterparker]

Affected part of DeckDeckGo

• [X] Studio
• [X] Remote control
• [X] Poll
• [X] Backend

Feature Description

We often have got Rollup problems because of socket.io-client which is not a modern library. Moreover socket.io doesn't seems that active anymore at first sight (last release of socket.io-client > 1.5 years old). Finally, Websocket is a standard.

That's why we should migrate from socket.io to Websocket

Open Questions

Do we want to make an intermediate step to a new Nodejs backend or do we directly integrate a new one in our AWS.

In case of the remote, don't forget the stun server.

Tutorial

Websocket: https://javascript.info/websocket

[peterpeterparker]

Another options is to rewrite everything and use HTTP Cloud Functions to exchange WebRTC and Poll information...