Add the RTT field to the RECV_RTCP_MESSAGE event emission which allows external listeners to compute MOS RTCP from the event.

This reverts commit c093b2d3.

RTCP/Receiver Report/lost field is a _signed_ 24bit integer and it could be negative (in case of UDP duplication)
+ any negatives now threated as huge uint32_t
+ set this field properly on __BIG_ENDIAN
+ correctly read this value in received RTCP on all arches

For outgoing calls send AES crypto in offer using corrected names
for keys of length 192 and 256, i.e. names containing _192_CM_
and _256_CM_ instead of _CM_192_ and CM_256_. For incoming calls
accept both naming conventions, decaying to same entry in SUITES.

Conflicts:
	libs/sofia-sip/.update

FS-10908: [mod_amqp] AMQP routing key (format_fields) formation broke and invalid reads reported by valgrind #resolve

FS-10865: [mod_conference] conference transfer event reports incorrect info in New-Conference-Name #resolve

FS-10749: [mod_amqp] Crash on unload after mod_amqp reloaded with  command + incorrect command behavior #resolve

FS-10867: [freeswitch-core] Prevent stack smash when queing multiple sound files without event-lock #resolve

FS-10860: [core] Distorted music when playing it as local stream into a conference as hold music #resolve

FS-10854: [mod_conference] Canvas FG Image not refreshed before writing to video recordings #resolve