[CLIENT-4082] CI/CD: run valgrind with a higher value for --num-callers option

[juliannguyen4]

TODO

• Merge tmrw on tuesday
• Try valgrind run with num-callers set to 500 to see whether 1) it's doable to check for memory leaks manually and 2) the run doesn't take too long

This prevents stack traces from being truncated. I noticed this happening when debugging memory leaks i.e the one found in PR #1067 coming from aerospike_info_foreach. All lines past the initial 12 lines in the stack trace get truncated, so I couldn't tell that this leak came from a Python client client.info_all() call.

Not setting --num-callers to the max value of 500 to prevent the logs from becoming too large.

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 84.44%. Comparing base (f1af021) to head (3790bce).
⚠️ Report is 7 commits behind head on dev.

Additional details and impacted files

@@           Coverage Diff           @@
##              dev    #1086   +/-   ##
=======================================
  Coverage   84.44%   84.44%           
=======================================
  Files          99       99           
  Lines       14062    14062           
=======================================
  Hits        11874    11874           
  Misses       2188     2188           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.