chore: graphql ws2

[nicolasburtey]

fix #1365, plus some security consideration using the old library: enisdenjo/graphql-ws#3

I ran into issues when I was importing both subscriptions-transport-ws and graphql-ws at the same time. instead of trying to understand the root of this, I decided to duplicated graphql-server and dynamically, at runtime, one or the other websocket library would be used.

by default the old library would be used - so that we can enable the use of the new library in another PR in the charts/deployment repo.

I recommend that we use a new url for BBW to do the migration from the mobile app. we could use api.bbw.sv to replace the current url. api.bbw.sv would have the graphql-ws library. mainnet.graphql.galoy.io would have the subscriptions-transport-ws library.

legacy server (when no env variable is set) --> api.mainnet.galoy.io
"new" server (when NEW_SERVER is set) --> api.bbw.sv

note: I didn't see there was a way to do backward compability with both subscription services

ws server usage with subscriptions-transport-ws backwards compatibility

[nicolasburtey]

may need to replaced with https://github.com/enisdenjo/graphql-ws

look at code example with #ws server usage with subscriptions-transport-ws backwards compatibility