Query Builder tests for OOM and memory limit

[grusev]

Reference Issues/PRs

What does this implement or fix?

Any other comments?

Checklist

Query Builder tests for OOM and memory limit

The PR contains code that introduces memray and pytest-memray libraries. With their help it is possible to create 2 types of tests:

• memory leaks test - the memory leaks tests will accept one or two parameters:

  • mem leak threshold - a threshold of mem in KB/MB that will trigger failure if above
  • (optional) filter function - the function can be passed to memray to filterout code that we do not want to be accounted as mem leak. In future we might get some code that we KNOW has memory leaks but is outside of our scope. Thus we can use this function to filter it out.. Currently the code accepts that mem leaks under certain treshold will not lead to failure. If that threshold is vialoted in future this should mean immediate development investigative task. In the log there will be information what is the code that triggered that. IMPORTANT: code source will be if the test is executed against release build - only the size of leak will be correct. To know the source of the code the test must be executed against build with debug information

• memory limit test - the memory limit test is about enforcing memory efficiency of code. Currently I have set CURRENT memory limit as limit for the this QueryBuilder code. If test fails in future then that would mean that our code is LESS memory efficient in that code. Why that has happened needs to be investigated Also, the number currently set accepts situation AS IS. It does not makes claim that we are memory efficient. No such study has been done it is outside of the test purpose. If such thing is needed then an investigative task need to be created

• Have you updated the relevant docstrings, documentation and copyright notice?

• Is this contribution tested against all ArcticDB's features?

• Do all exceptions introduced raise appropriate error messages?

• Are API changes highlighted in the PR description?

• Is the PR labelled as enhancement or bug so it appears in autogenerated release notes?

[grusev]

Close in favor of #2054 where the PR is moved