Until now we only logged for `normal`, `danger` and `critical` leading to some ambiguity in log analysis

Here's what we do when user activates mic:
1 - When we do something similar to listenonly's joining process
until we find a valid candidate-pair. The information about this
local candidate is store.
2 - We then start a new userAgent, and as soon as browser finds
a candidate with the same local ip address, we leave only this
candidate in the SDP and send this to FreeSWITCH. SDP should
contain only a single candidate.
3 - The rest of signaling process is basically the same.

When the answer is not default (Custom or UserResponse), don't translate the answers.

Fix prolems with ":" char in answers.
Respect poll question formatting (lineBreaks/spaces) in other fields of UI

BigBlueButton v2.3 uses an instance prefix while generating padIds. Closed
captions was missing this information when updating pad's content for dictation
mode.

This interaction occurs between Etherpad and Meteor.

Add PollPublishedRecordEvent with all infos (also fix duplicated handlePollStoppedEvtMsg)
Add answer text to UserRespondedToPollRecordEvent (useful for custom answers)
Add type in PollStartedRecordEvent