Implement Proxy Mode

[qdot]

Allow buttplug-js to sort of reverse-proxy its server.

• buttplug-js server would connect as a websocket client (but Buttplug Server) to a desktop relay app.
• Other actual client desktop applications could connect to the desktop relay app.
• This would allow using the phone as a bluetooth device server via a webpage, while still using desktop apps.

This would only work on android, but means any time buttplug-js updated, we wouldn't have to do an app release, we could just update the relay webpage.

An Example:

A Windows 7 user wants to use their Launch with ScriptPlayer (https://github.com/FredTungsten/ScriptPlayer). However, using the Launch with Bluetooth on a desktop is only supported on Windows 10. The user also has an android phone.

• They bring up the Buttplug Web Relay application (a native C# application) on their desktop. This application acts as a Websocket server.
• They then bring up the Buttplug Web Relay Website on their android phone. This website contains the Buttplug-js library, as well as a way to connect via Websocket to the application on the Desktop.
• They connect the website on the phone to the app on the desktop via an interface on the website, using a special port to signify the connection will act as the server.
• They then bring up ScriptPlayer, and connect it via either Websocket or IPC (Named Pipe) to the Relay app on the desktop, using a special port to signify the connection will act as a client.
• Now ScriptPlayer can use the phone as a bluetooth device access point.

[qdot]

Used to be at https://github.com/buttplugio/buttplug/issues/69

[qdot]

@AlexanderPavlenko A lot of the info in this bug is super old, and doesn't really reflect our current architecture anymore. The new proxy system will most likely be WebRTC based, so the only thing that has to sit in the cloud is a STUN/TURN/ICE server which probably won't do all that much. It's a system that https://xtoys.app has already proven out w/ good success, so now it's just down to me implementing it.

This will reflect something similar to our device forwarder system in https://github.com/qdot/simple-teledildonics-app, just using P2P instead of bouncing through websockets.