In WT-10340, we added messages for sessions that "did not run a sweep for 60 minutes", to try to diagnose "rogue" sessions.  The message uses the WT_SESSION->name to show a (supposedly) helpful message.  But this session field is only set when running an internal WT session, it is not user settable.  We should consider having a WT_CONNECTION->open_session config like "name=..." to allow applications to set names, and perhaps have the session name be visible in more messages, our at least available when there is a callback.

The specific example to motivate this was noticed by louis.williams@mongodb.com . MDB has a session that is used to flush the journal.  It doesn't have any cursor activity, so can't really be a "rogue" session.  The message pops up after about a minute from when mongod starts.  It would be good if the message was tagged with the session name so we would know that it was benign.