Summary
The timestamp manager is currently defined as a component in the cppsuite. This means it can be enabled/disabled through the configuration file and has a load, a run and a finish phase. However, when we disable the timestamp manager, we don't really do it. We allocate memory for it in the constructor of the test class and pass it as an argument in different objects.

The run phase of the timestamp manager updates the oldest and stable timestamps, we should probably let the user have control over this. This could become a database_operation function. We would keep the timestamp manager as an interface with the WT APIs to interact with timestamps. It could become a singleton.

Motivation

• Is this issue urgent?
  No

Acceptance Criteria (Definition of Done)
Decide on what to do with the timestamp manager so the code is less coupled and its purpose makes more sense.

• Documentation update
  Check the documentation written as part of WT-9109 and WT-9111