In looking at the situation posed by HELP-39798, we would like to know if there are any "rogue" sessions, that have not run one of their sweeps for a long time.  MongoDB should either be using a session regularly (and thus its sweeps should run) or it should eventually close any non-used session.  Also, sessions that are currently "in-use" should not run a long time between calls to session.reset().  If either of these are violated, there is a chance that a sweep will rarely or never run.  Each session stores the time that the last sweeps were run.  Maybe the connection level sweep could also walk through the list of sessions and identify any that had a long time since the last sweep (maybe have a statistics count for each "5-minute" violation it found and a different counter for any "60-minute" violation.  Any of these would point to a violation of our assumptions for session use, and let us know the severity of the violation.  WT-10253 ensures that sweeps are run even if a session is used occasionally.  To verify that and also to track "rogue" sessions that don't play by the rules, we need these new stats.