fix: use consistent log format for TIME prints

...it make it easier to process the logs in automated way.

JitsiConferenceEventManager.js

         const key = 'data.channel.opened';
 
         // TODO: Move all of the 'connectionTimes' logic to its own module.
-        logger.log(`(TIME) ${key}`, now);
+        logger.log(`(TIME) ${key}:\t`, now);
         conference.room.connectionTimes[key] = now;
         Statistics.sendAnalytics(
             createConnectionStageReachedEvent(key, { value: now }));

modules/xmpp/strophe.jingle.js

             break;
         }
         case 'transport-replace':
-            logger.info('(TIME) Start transport replace', now);
+            logger.info('(TIME) Start transport replace:\t', now);
             Statistics.sendAnalytics(createJingleEvent(
                 ACTION_JINGLE_TR_RECEIVED,
                 {
             sess.replaceTransport($(iq).find('>jingle'), () => {
                 const successTime = window.performance.now();
 
-                logger.info('(TIME) Transport replace success!', successTime);
+                logger.info('(TIME) Transport replace success:\t', successTime);
                 Statistics.sendAnalytics(createJingleEvent(
                     ACTION_JINGLE_TR_SUCCESS,
                     {

modules/xmpp/xmpp.js

     attach(options) {
         const now = this.connectionTimes.attaching = window.performance.now();
 
-        logger.log(`(TIME) Strophe Attaching\t:${now}`);
+        logger.log('(TIME) Strophe Attaching:\t', now);
         this.connection.attach(options.jid, options.sid,
             parseInt(options.rid, 10) + 1,
             this.connectionHandler.bind(this, {