fatal error: runtime: out of memory (GHC bug)

### Version Information

Server Version: 2.0.9 & 2.2.2

### Environment

AWS Elasticbeanstalk
t3.xlarge EC2
Ubuntu 20.04
Docker 20.10.17

### What is the expected behavior?

Normal operation :)

### Keywords

hasura, GHC crash, fatal out of memory, sadness

### What is the current behaviour?

During normal production workloads hasura crashes with error.
This is despite there being plenty of resources available on that ec2

### How to reproduce the issue?
:(
Currently unknown how to reproduce, would be helpful if there were better debugging commands to replay queries before crash? I will look this up.

### Screenshots or Screencast


### Please provide any traces or logs that could help here.

### Any possible solutions?

### Can you identify the location in the source code where the problem exists?

### If the bug is confirmed, would you be willing to submit a PR?

We most likely don't have the relevant experience to create a fix :/

No source file, test, or entry point is identified, and the crash is currently unreproducible. Start by reviewing the reported GHC out-of-memory logs and deployment details for Hasura 2.0.9/2.2.2 on AWS Elastic Beanstalk, then establish a reproducible workload or diagnostic process; done requires identifying a confirmed cause and a validated fix.

Written by the indexing model from the issue text.