While investigating WT-6412, alexander.gorrod pointed out that in some cases traversals of the history store never see any content. We suspect that there is a gap in our actual implementation of history store visibility checks and how we expected them to work. The check in __txn_visible_id isn't what is expected for operations on the history store and due to this check we often won't see any value unless it's globally visible.

We get away with it because we short-circuit the visibility check in __txn_visible_id in many cases for the history store via a check in __wt_txn_upd_visible_type

The aim of this ticket is to understand what needs to be done to bring history store visibility checks closer to expected behaviour.