[DEVOPS-234] CI/CD: Reuse builds for feature branches in Github Actions workflows

[juliannguyen4]

Reason for this change: it will be a while to clean up all the memory leaks while running the Python client regression tests, and we normally run valgrind manually. We won't be running valgrind as a CI/CD check for a while because of this. Often times, the valgrind workflow builds a wheel when a wheel was already built for the same commit. This change forces valgrind to reuse a wheel (from JFrog) if it already exists

• Code reviewed
• First valgrind run builds new wheel
• Second valgrind run uses wheel built in first run
• When there are two wheels for the same commit, the one with no labels is used
• No regression when running valgrind run on central branch

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 80.89%. Comparing base (d1e7bc2) to head (33a70d3).
Report is 16 commits behind head on dev.

Additional details and impacted files

@@            Coverage Diff             @@
##              dev     #670      +/-   ##
==========================================
- Coverage   80.96%   80.89%   -0.08%     
==========================================
  Files         100      100              
  Lines       15130    15053      -77     
==========================================
- Hits        12250    12177      -73     
+ Misses       2880     2876       -4     

Flag	Coverage Δ
	80.89% <ø> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

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