Move the mixed-content blocking checks from synchronous Init to asynchronous InitializeConnection in WebSocket.cpp. This aligns the behaviour with the standard specifications where mixed-content failures trigger asynchronous error rather than throwing a synchronous SecurityError during WebSocket construction Differential Revision: https://phabricator.services.mozilla.com/D308017