fix race condition where a transferring leg could be hungup on by the bridge partner from the previous bridge because of hangup held leg detection.  The leg which was hungup when held doesn't realize the other leg has already moved on from the bridge because it was transferred and is already on its way to connect to the new destination

Our sqlite fork was reading past the end of the zP3 KeyInfo structure
here.  This was causing gcc and clang's address sanitization to alert.

FS-6279 --resolve

Thanks-to: Christopher Rienzo <chris@rienzo.net>

Revert the changes I made the issue is in the build system not in this script if DESTDIR is used will re-eval the correct approach.

rtp_secure_media=true
--inbound: Accept the srongest supported offered crypto suite, MUST result in a negotiated crypto or aborts.

--outbound: offer all supported crypto suites, MUST result in a negotiated crypto or aborts.

rtp_secure_media=optional
--inbound: Accept the srongest supported offered crypto suite, fall back to no crypto if no valid ones accepted.

--outbound: offer all supported crypto suites, OPTIONAL result in a negotiated crypto falls back to no crypto.

rtp_secure_media=<suite1>,<suiteN>
--inbound:  same behaviour as rtp_secure_media=true with smaller set of acceptable suites.
--outbound: offer supplied crypto suites, same behaviour as rtp_secure_media=true with smaller set of suites.

FS-5934 force_transfer_context not being honored if you happen to do an attended this patch makes perfect sense.

fix modcheck to properly deal with prefix and don't alert on anything that isn't mod_ because ftmod_ gets installed here too and will alert

FS-6271 --resolve Adding support for smoothing the min-cpu-idle by X number of seconds. Adds the cpu-idle-smoothing-depth into the conf/autoload_configs/switch.conf.xml configs with a default value of 30 seconds.

FS-6275 --resolve  I don't think this is a problem with latest firefox + latest master but i'll ensure it with this change.  Anyone into testing webrtc should always use master until an official 1.4 is released.

Can be enabled with 'queue-capacity' param
Cdrs can be pushed to the queue and posted in a separate
thread to avoid bllocking the session with a slow web server

This reverts commit fa921711.