Summary
After some cpp changes, fallouts were not detected as part of the PR testing. The issue was faced after a first attempt at merging WT-9384. We already have cpp tests as part of the PR testing but we have an Evergreen task per test using the "-t" argument. We are missing a task that executes each test one after the other (this can be done if the "-t" argument is not specified).

Motivation

• Does this affect any team outside of WT?
  No

• How likely is it that this use case or problem will occur?
  Every time there are code changes in the cpp test framework

• If the problem does occur, what are the consequences and how severe are they?
  Tests that include the cpp ones might fail.

• Is this issue urgent?
  Not sure, this is just to avoid breaking the cpp framework when we make changes to it.

Acceptance Criteria (Definition of Done)
We could add a simple test in our Evergreen file that simply calls the cpp executable "run" without specifying the test to run. This executes all the cpp tests using their default configuration. It should not impact the PR testing time too much as the default test configurations are not stressful and each test is limited to be executed for 60 secs.