Hasura Engine RAM consumption grows indefinitely

### Version Information
VERSION=v2.33.3
Server Version:
VERSION=v2.33.3

### Environment
Kubernetes deployment.
Nothing special in charts or values...

### What is the current behaviour?
While CPU consumption resembles the actual load, the RAM consumption grows indefinitely
Such behaviour became apparent after HPA limits were raised. Otherwise, K8s just kills pods very frequently.
Such behaviour drives managed Postgres instance crazy too.

### What is the expected behaviour?
Service resource consumption rise and fall together with load

### How to reproduce the issue?
Deploy hasura instance in K8s and apply intermittent load. Wait for a couple of days.

### Any possible solutions/workarounds you're aware of?
We have been struggling with issues related to Hasura stability for some time. We tried to adjust queries and parameters in our services but it did not change the picture. Pods were dying.
However, after we significantly raised HPA limits for Hasura, pods stopped dying but our database management started to go in 'failover mode' out of blue and graph started showing such steady consumption growth.
As of now, the workaround is to kill pods as soon as they become 3 days old.

Please consider fixing it.
Also, are there average numbers for Hasura consumption and other metrics.

Thank you!

### Keywords

RAM, resource consumption

Reproduce v2.33.3 in a Kubernetes deployment with intermittent load over several days, while monitoring Hasura RAM, pod restarts, HPA behavior, and managed Postgres failovers. Done means resource consumption rises and falls with load rather than growing indefinitely, with a focused regression check for the observed behavior.

Written by the indexing model from the issue text.