Enable local cors policy on dev pdr-websockets

[idiom-bytes]

Problem

Local dev environments should easily connect to dev BE.
Right now, CORS policy blocks local dev.

Solution:

Enable cors policy when deploying in dev environment (GCP VM)

DoD:

• Local dev client (pdr-web) should connect to dev BE

[KatunaNorbert]

Can't reproduce this issue. Are you on the right branch?
I run pdr-web locally and connected to dev websocket. Also run websocket locally and connect it to dev backend and local pdr-web. I also had a PR to add CORS to websocket API.

Private Zenhub Image

[idiom-bytes]

Yes, I'm still getting this

Access to fetch at 'https://development.oceandao.org/socket/api/v1/initial' from origin 'http://localhost:3000' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.

I'm running off a pretty fresh pdr-web.

I'm trying to connect to remote: development.oceandao.org websocket, development.oceandao.org/subgraph, and development.oceandao.org ganache.

[idiom-bytes]

We're currently ignoring these issues in dev-environment as it's not required for the app to work.

However, if we're testing development, we might want to update cors policy on websockets server to support cors from local