Properly deal with the "fake / pilot stream" created by Chrome

[DamonOehlman]

When quickconnect is used in reactive mode, and no data or media is added prior to creating a connection it is common to see a stream:added event for a fake stream that is added by Chrome to assist with correctly negotiating ice connectivity for the peer connection.

At this stage this new default stream is triggering a stream:added event when first created, but is no stream:removed event when the fake stream is replaced by a real media stream. This needs to be investigated and resolved so that either the stream:added event is never triggered for the connection (see previous investigation in #31) or a stream:removed event is triggered once real media starts to flow (the second approach being more realistic).

ref: rtc-io/rtc-screenshare#2 +@santhoshreddyk