Add a new workflow for testing the release workflow

[yurishkuro]

Which problem is this PR solving?

• Part of Use larger GitHub runner for the release workflow #5529. Right now there is no way to test the release workflow outside of actually doing a release.

Description of the changes

• Refactor CI scripts for better control of "test runs"
• Add a new release testing workflow that does not attempt to publish artifacts

How was this change tested?

• CI

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 96.20%. Comparing base (6b95711) to head (5ebf94b).

Additional details and impacted files

@@             Coverage Diff             @@
##             main    #5532       +/-   ##
===========================================
+ Coverage   54.25%   96.20%   +41.94%     
===========================================
  Files         161      327      +166     
  Lines        8366    16007     +7641     
===========================================
+ Hits         4539    15399    +10860     
+ Misses       3381      432     -2949     
+ Partials      446      176      -270     

Flag	Coverage Δ
badger_v1	8.05% <ø> (ø)
badger_v2	1.93% <ø> (ø)
cassandra-3.x-v1	16.45% <ø> (ø)
cassandra-3.x-v2	1.85% <ø> (ø)
cassandra-4.x-v1	16.45% <ø> (ø)
cassandra-4.x-v2	1.85% <ø> (ø)
elasticsearch-7-v1	18.89% <ø> (ø)
elasticsearch-8-v1	19.09% <ø> (ø)
elasticsearch-8-v2	19.09% <ø> (+0.01%)	⬆️
grpc_v1	9.48% <ø> (+0.01%)	⬆️
grpc_v2	7.52% <ø> (-0.02%)	⬇️
kafka	9.77% <ø> (ø)
opensearch-1-v1	18.94% <ø> (+0.01%)	⬆️
opensearch-2-v1	18.94% <ø> (ø)
opensearch-2-v2	18.94% <ø> (ø)
unittests	94.07% <ø> (?)

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.