Use 'sendToAll' for 'session.restart' and 'session.terminate' events.

Not doing so will cause issues when trying to mute after
'session-terminate', because the PeerConnection is closed and should not
be used anymore.

When call ends the PeerConnection is closed and the SSRCs stored in
the local track will not match those assigned the PeerConnection when
it's reopened for new session. This will confuse SSRC replacement logic.
We need to reset those SSRCs and re-register 'ssrcHandler' listener to
get the new ones.

The event is triggered when Jicofo sends 'session-terminate' and our
PeerConnection is closed.

Also adds a safe check if there was no regionInfo to skip reporting cross-region.

removed white space
redid the hooking of the Transcribing module to JitsiConference
redid the exposing of the Transcribing module to JitsiMeetJs

Updates removeTrack to always clean properties and resources even when there is no room available.

Need to attach the listeners after statistics is created.

Handle case when JitsiLocalTrack#dispose() is called after track was removed from conference.
Set track's conference reference to null when removing track from conference.

If the API client happened to try to add one and the same local video
track twice, the library would throw an error. I find that draconian
because:

1. The error message states that a second local video stream cannot be
added but that is incorrect because the API client is not trying to add
a second local video stream but add one and the same local video stream
multiple times.

2. The jsdoc says that a throw will happen if another local video stream
is added but that is misleading because the API client is not trying to
add another local video stream but add the same local video stream.

3. Adding one and the same local video stream multiple times can be
handled gracefully by the lib-jitsi-meet library. Thus, the library
appears more friendly.

Hence, gracefully handle the case of adding the same local video track
multiple times without throwing an error.