WebSocket version migration

[leonhard-s]

In recent versions of Python, the SSL certificate bypass hack from #55 no longer works, and the default context used can even prevent successful connections entirely.

As a hotfix, the bypass will be disabled in the next version. This should not cause any interruptions to clients as the certs are still good for a few more months (and maybe will be updated this time, rather than expiring).

A more comprehensive fix will follow in conjunction with a migration to the new websockets API. Auraxium is currently using the legacy client-based interface for connections, and any SSL context customization required is tied to it, so might as well do both rather than having to re-do it in a few months anyway.

[leonhard-s]

A note regarding the FutureWarning raised when specifying no_ssl_certs=True in Auraxium v0.2.2:

This warning is primarily intended to inform the user that the bypass is currently inactive. Future versions will likely still use this syntax and no changes to client code will be needed.