SocksToRtc-style lifecycle and unit tests for RtcToNet

This pull request is to RtcToNet as the following pull request was to:
https://github.com/uProxy/uproxy-networking/pull/137

Of course, the RtcToNet "server" has only one dependency: the peerconnection. Also remove code related to control channel which is now handled by peerconnection.

Tested with `curl` and a quick browsing session on Firefox.

I will tackle RtcToNet sessions in a followup.
Shouldn't the fulfill stoppping also close all sessions (else you get left with dangling tcp connections? )