FS-11421: [core,mod_sofia] Fix rtp_pass_codecs_on_stream_change to process all sdp settings in the re-invite -- add new filter_codecs app and fix some races and negotiation bugs #resolve

FS-11438: [freeswitch-core] recvonly channels left that way on blind transfer in some cases #resolve

FS-11509: [Build-System] Fix unimrcp build with address sanitizer.

* commit 'f3c52d57':
  FS-11874: [Verto-Communicator] Rebuild verto-min.js to reflect the latest changes to js.

Merge pull request #1738 in FS/freeswitch from ~THEHUNMONKGROUP/freeswitch:bugfix/FS-11874-faulty-logic-for-checking-addition-of-multiple-mediastream-objects to master

* commit '8fdc4433':
  Fix FS-11874

Verto JS libs allow passing an attachStreams array of MediaStream objects, which are then supposed to be added to the peer connection in the order they are supplied in the array.

However, there is a faulty logic check prior to actually adding the streams, where 'options.attachStream' is checked for length instead of 'options.attachStreams'.

Merge pull request #1737 in FS/freeswitch from ~THEHUNMONKGROUP/freeswitch:bugfix/FS-11873-addstream-adds-audio-video-tracks-in-random-order-use-spec-compliant-addtrack to master

* commit 'f1bc56d6':
  Fix FS-11873: addStream() adds audio/video tracks in random order

addStream() is a deprecated WebRTC API method, and only works via shimming on some platforms. Internally, it is inconsistent in building an offer SDP in the order which FreeSWITCH expects it, which is audio m-lines first.

This can result in intermittent m-line ordering errors on the client.

Instead addTrack() can be used to force the media tracks to be added to the peer in the order FreeSWITCH expects.

Merge pull request #1735 in FS/freeswitch from ~MITCH.CAPPER/freeswitch:FS-11865-fix_mod_com_729_bin_url_change_pr to master

* commit '1f0dea99':
  FS-11865 [mod_com_729] change to use latest version for mod_com_g729 bins so url does not go stale and update new binary paths