Run all tests in release build in long suite on master merge

Historically we've been focused on debug-build tests, under the assmption that it is pretty rare for an issue to happen only in release build. Debug build has extra checks that catch more errors. Today we run only a subset of tests in release build, based on that assumption and to keep the PR CI time down. But: we have a separate "long" suite on master merge where the time doesn't matter as much. We should enable all the tests in release-build there.

This is becoming more important as we have lately been seeing release-build-only failures: #4928, #4954, #2417 drcachesim.coherence.

Start by locating the long suite that runs on master merge and inspect how it selects release-build tests. Compare that selection with the debug-build suite and the current release subset, then verify that the long suite runs all tests in release mode, including drcachesim.coherence; related failures are #4928, #4954, and #2417.

Written by the indexing model from the issue text.