Report an error when js-waku is running over http and hence cannot connect via WSS

[vpavlin]

This is a **change request** ## Problem When a js-waku app is ran on HTTP (not HTTPS) and also not `localhost` connection-manager will silently fail to connect to any node. This is visible when `debug:waku*` is enabled, but not in "production" setting ``` waku:error:connection-manager Error dialing peer 16Uiu2HAmSve7tR5YZugpskMv2dmJAsMUKmfWYEKRXNUxRaTCnsXV - Error occurred during XX handshake: Error occurred while verifying signed payload: TypeError: Cannot read properties of undefined (reading 'digest') +0ms ``` ## Proposed Solutions Surface an error/warning about not using HTTPS and hence not being able to connect to any peers to the dev/user ## Notes

[weboko]

Let's confirm that full nodes advertise ws connection and not only wss.

In nwaku-compose - https://github.com/waku-org/nwaku-compose/blob/8abb2a474d9bf9f9acc5c3a8bc03c4eda015551d/run_node.sh#L36

Todo:

• make sure local development over HTTP works;
• double check that ws connection can be established if advertised by node;
• if problem persists with establishing connection from http to ws we should add warning;