If there's no capabilities version mapping to user's jid
still allow to discover features (that's the case for Jicofo).

* ref: Fix imports order.

* feat: Adds display name required connection event.

The version change is invoked from add/remove features which controls whether to submit the presence.

Attempts to fix this race condition:
1. Web client joins a conference.
2. Electron client joins the same conference.
3. Web client requests capabilities of Electron
   using version 1111.
4. Electron adds remote control capability,
   settings its version to 2222.
5. Electron responds to web client's requests
   but with features of 2222.
6. Web client caches request under 1111.
7. Any future calls to get features for a client
   with version 1111 will incorrect include the
   remote control capability.

When the main domain advertises component with type 'speakerstats' every participant will send message to the component with the name of the room where this happen.

ESLint 4.8.0 discovers a lot of error related to formatting. While I
tried to fix as many of them as possible, a portion of them actually go
against our coding style. In such a case, I've disabled the indent rule
which effectively leaves it as it was before ESLint 4.8.0.