Automated memory leak testing

Customers occasionally report memory leak issues. It would be ideal to proactively detect these before customers hit them. It would also be easier to debug them if we could find them closer to when they enter the code base.

Having a CI job on PRs for this would be convenient to find issues before they get merged in, but may be challenging if we need the test to run for a longer duration before we can identify a memory leak.

Another challenge is coming up with the right set of queries to run. Having a framework to test for memory leaks would give us a good base to build on and we could easily extend the query set as needed. Another option could be using the fuzzer to generate more variety in the queries.

A memory leak detection test could run all the queries and tell us whether any memory leak was detected, or it could separately run different sets of queries to tell us that a memory leak was detected for a specific query type, which would make debugging the leak easier.