Straighten out muting to prevent echo when crossing from vivox to webrtc regions near a webrtc region boundary.

[roxanneskelly]

Muting was a bit random in the code, so it's now been straightened out and should prevent echo.

Also, code was added to not attempt connection to non-webrtc regions in the webrtc code.

Description

Fix for issue #4419

When crossing from vivox to webrtc regions, the send connections were both being set to enabled,
which resulted in echo. This was because of poor mute state handling.

Also, the code was attempting to connect to webrtc on neighboring vivox regions.

Related Issues

• Please link to a relevant GitHub issue for additional context.
  • Bug Fix: Link to an issue that includes reproduction steps and testing guidance.
  • Feature/Enhancement: Link to an issue with a write-up, rationale, and requirements.

Issue Link: #4419

Repro Steps:

• Find two neighboring webrtc regions with yet another neighboring vivox region.
• Log in with two viewers in one of the webrtc regions.
• Walk one agent across the webrtc->vivox boundary and back.
• Validate there is no voice duplication or echo.

Also, cross-webrtc-region voice should be validated.

• Any dependent changes have been merged and published in downstream modules
• I have reviewed the contributing guidelines.

---

Additional Notes