BroadcastProtocol introduction

[jiivan]

No description provided.

[maaktweluit]

LGTM!

Small comments, please fix or reply before merge

Approving to get those full tests running

[codecov]

Codecov Report

❗ No coverage uploaded for pull request base (develop@6f4df24). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             develop    #5109   +/-   ##
==========================================
  Coverage           ?   89.89%           
==========================================
  Files              ?      237           
  Lines              ?    22321           
  Branches           ?        0           
==========================================
  Hits               ?    20065           
  Misses             ?     2256           
  Partials           ?        0           

[etam]

FYI this are the current state machines:
SessionProtocol:

BasicProtocol:

ServerProtocol:

BroadcastProtocol:

[etam]

I've cleaned up them a bit. What you think?

SessionProtocol:

ServerProtocol:

BroadcastProtocol:

EDIT: jiivan is right, that from initial and handshaking states must be a transition to disconnected, that has no callbacks.

[etam]

In the next step we could add an integration test.

[kmazurek]

@jiivan Looking through the logs of the last test run I noticed that transitions logs seem to be going to INFO level by default, e.g.:

INFO [transitions.core                   ] Exited state initial
INFO [transitions.core                   ] Entered state handshaking
INFO [transitions.core                   ] Exited state handshaking
INFO [transitions.core                   ] Entered state connected

They seem to be unnecessary for end users and will also attribute to log spam as multiple lines will be printed for each connection.