[FIX] Remove stack traces from Meteor errors when debug setting is disabled

[matheusbsilva137]

Proposed changes (including videos or screenshots)

• Fix 'not iterable' errors in the normalizeMessage function;
• Remove stack traces from errors thrown by the jitsi:updateTimeout (and other Meteor.Errors) method.

Issue(s)

Task - ClickUp
Fixes #19441

Steps to test or reproduce

1. Create a room and add a member to it;
2. Members > select the added user > Mute User;
3. Login as the muted user and start a Call in the new room;
4. If the room is read-only, the following error will be thrown: server.js:204 System ➔ error Error starting video call: You can't send messages because the room is readonly.
   Otherwise, the thrown error will be: server.js:204 System ➔ error Error starting video call: You_have_been_muted (stack traces from Meteor.Error have been removed).
   The Meteor stack trace is still shown if the admin user chooses "2 - Errors, Information and Debug" in Administration > Logs > Log Level.

Further comments