Build and Test changes for flaky test investigations

[grusev]

Reference Issues/PRs

What does this implement or fix?

The purpose of this PR is to allow execution of tests until they fail through our standard Build and Test workflow.

To use this just add your changes to this PR, and then execute manually the workflow through Actions tab.

• update to latest the code
• make sure to select 'test_falkyness' branch
• if test is AWS or GCP select the proper type, if not leave dropdown to no
• at the last input box write custom pytest line like folloing:

pytest -n auto -v --count=100 -x python/tests/integration/arcticdb/test_storage_lock.py
# place your the number of repetitions for the test
# change the test accirding to your needs

• Start execution

The exeution will start and on each leaf container the test you pick will be executed the number of times you chose. It will fail the first time a failure is detected. Timeout is 6 hrs by default

---

Test : python/tests/stress/arcticdb/version_store/test_mem_leaks.py::test_mem_leak_read_all_arctic_lib
Command : pytest -n auto -v --count=15 -x python/tests/stress/arcticdb/version_store/test_mem_leaks.py::test_mem_leak_read_all_arctic_lib
Log : https://github.com/man-group/ArcticDB/actions/runs/15444359252

=================================
Test: python/tests/integration/arcticdb/version_store/test_basic_version_store.py::test_version_chain_cache
Command: pytest -n auto -v --count=100 -x python/tests/integration/arcticdb/version_store/test_basic_version_store.py::test_version_chain_cache
GCP Log: https://github.com/man-group/ArcticDB/actions/runs/15446172552/job/43476877668
AWS Log: https://github.com/man-group/ArcticDB/actions/runs/15458674848

Any other comments?

Checklist

Checklist for code changes...

• 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?