Bring local graphql-engine version into sync with production / latest version

[frankhereford]

Associated issues

This issue is the root cause of this change, but does not directly address it.

This is a change that we would normally do during a release party directly into master, but due to our recent upgrade to the graqphql-engine middleware, this is needed to spin up the local stack with a replicated or copied database from production.

Testing

Steps to test:

• Spin down your graphql-engine endpoint locally
• Replicate the production database into your local database via a backup fround on S3 or pulled directly from the read replica. ./vision-zero replicate-db
• Check to see if your local graphql-engine starts up

---

Ship list

• Code reviewed
• Product manager approved

[mddilley]

This lines up with the version that I used to init the migrations so I'm approving based on that testing. Thanks for the cleaning up the comments too! ✨

[patrickm02L]

Good to go 🚢