feat: return email subscription data in User

[wa0x6e]

Toward https://github.com/snapshot-labs/workflow/issues/226

This PR returns email subscriptions data from envelop, directly from the hub, in the user(s) object.

Instead of sending an extra query to fetch user email subscription info, we can know get if from the hub with

query { 
  user(id: "0x91fd2c8d24767db4ece7069aa27832ffaf8590f3") {
    id
    name
    emailSubscription {
      status 
      subscriptions
    }
  }
}

Which will return something like

{
  "data": {
    "user": {
      "id": "0x91FD2c8d24767db4Ece7069AA27832ffaf8590f3",
      "name": "℞aphaël-Daniel de la Poubelle『⚡』",
      "emailSubscription": {
        "status": "VERIFIED",
        "subscriptions": [
          "summary"
        ]
      }
    }
  }
}

In case user is not subscribed, it will return

{
  "data": {
    "user": {
      "emailSubscription": {
        "status": "NOT_SUBSCRIBED",
        "subscriptions": []
      }
    }
  }
}

Returning email subscription data from the hub will avoid having to manage another read API on sx side.

A sister PR (snapshot-labs/snapshot.js#1081) will merge the write function inside sequencer.

NOTE

The envelop DB connection is optional, and will always return data as NOT_SUBSCRIBED if not present (useful for the testnet)

TODO

• In prod, set ENVELOP_DATABASE_URL= to envelop mysql database url

[codecov]

Codecov Report

Attention: Patch coverage is 34.00000% with 33 lines in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
src/graphql/operations/users.ts	0.00%	33 Missing ⚠️

Additional details and impacted files

📢 Thoughts on this report? Let us know!

[bonustrack]

Can we make the config var optional so we don't enable it on testnet hub?

[wa0x6e]

Done, envelopDB connection is now optional

[ChaituVR]

Done, envelopDB connection is now optional

I think we need to address snapshot-labs/snapshot-sequencer#470 first no?