* ignore duplicate jibri status updates

* re-add mistakenly removed return

* ref(recording): change implementation to match VideoSIPGW

VideoSIPGW takes in a chat room and uses instance variables
on the chat room. RecordingManager has been changed to
mirror this approach because of the case where jitsi is
deployed on a domain requiring authentication. In that
case, the initial chat room is created and fails, a
new chat room (connection) is created for authentication,
authentication is put onto the failed chat room, and the
failed chat room is used. As such, recordingManager
should not be tied to chat room creation itself but
rather tied to the first chat room.

* squash: use git mv to detect capitalization change

* feat(recording): frontend logic can support live streaming and recording

Instead of either live streaming or recording, now both can live together.
The changes to facilitate such include the following:
- Remove the old recording.js module which allowed one recording at a time.
- Remove events for live stream url changes as the url is now part of a
  sesssion and not fired independently.
- Availability of sipgw and recording are gone. Instead sessions have a
  failure reason. For sipgw sessions, store that failure and emit it to
  listeners.
- Create a new recordingManager singleton that can start/stop sessions
  and handle updating known state of those sessions. Known state is
  emitted through one event.
- Create a JibriSession model to encapsulate state of a session.

* update comments, use map to store sessions

* always pass in focusmucjid

* try to fix jibrisession docs and remove default null