Make the bridge more robust for attempted repeated connects

When someone quickly refreshes a web browser with an active develex-core library, the WebSocket connection between the client and the bridge is not considered to be interrupted.

However, the client needs to reestablish the connection. That will lead to duplication of processes. Meaning that the bridge will send to the same client the same data twice.

Desired outcome:

1. On connect request, the bridge will check whether there is already a connection to that client
2. If so, end the previous one and start a new connection with the new config
3. Send the confirmation back to the client

This is also important if anyone changes a configuration halfway to a walkthrough and needs to reinitialize an eye tracker input.

This can be changed if you prefer other ways of solutions. Just prevent the duplication.