fix #49

The `getMyId` method had incorrect case. It caused errors since it was
called with a different (correct) case elsewhere.

Fix case.

client/lib/live-reco.js indent was all screwed up. fixing it.

No actual code change.

Online reco method will now return a boolean indicating of the method succeded
or failed.
When starting online reco, if it fails, it will be tried again at fixed
intervals.

robot now displays some log when initialized.

Refactored `recordParticipant` in order to extract two independent functions for
getting a STT WS and recording the user stream.

On STT WS error, try to get a new STT WS for the user.

STT lib mock is now extracted into a separate object for cleaner handling.

Previously hublot would record and try to transcribe it own media stream. Add
check to avoid this.

Add the `getMyId` function to the controller in order for hublot to know its own
participant Id.

Robot will now stop recording and close websocket when a participant leaves the
room.

robot now checks for participants that have already joined the room and record
them on start.

There was a (non-problematic) typo in `should start transcribing stream on user
connection after start` test in `robot.test`.

Fixed it.

robot now displays reco. as chat messages

The client controller now exposes a function to send a chat message via hublin.

Extract keywords and propose recommendation links based on transcription segments which are sent by the participants

The external libs would not get loaded before running the behavior functions
that required them.

Move loading function call and add timeout to force them to get loaded before
robot start.

robot now initialize lib.archive on start

Add client lib to archive transcripts of meetings.

Add `client/external.js` which load third-party scripts passed into the
`externalLibs` array of the client config object.

Implement first version of robot behavior. Currently, the robot listen for new
participants and, when a participant connect, start speech recognition.

The results of speech recognition are displayed in the console.

The robot requires the `start()` method to be called to begin. This method is
automatically called by the runner after loading all the modules.