After WT-10545, we are now returning an error message when the checkpoint cursor hangs due to mismatching information.

This ticket suggests an alternative solution: if a previous checkpoint exists, try to open the checkpoint cursor on it. Try this until the list of checkpoints is exhausted. If none succeeds, an error can be returned.

There are specific scenarios to consider:

• When a named checkpoint is given to the checkpoint cursor, it should succeed.
• When an unnamed checkpoint is given:
  • If it is an internal call, this should succeed.
  • If it is an external call, the name should be WiredTigerCheckpoint (see WT-10637). This means the latest checkpoint has been requested. If this one cannot be opened for any reason, try a previous one.