SERVER-45367 was only committed in v3.6 and v4.0, hence in currently supported versions we're missing the list of cursors retaining a range deletion that is a very valuable information in case the range-deleter is slow or gets stuck.

Purpose of this ticket is to add the information and evaluate whether to build a more complex machinery to not only log cursors when a range deletion starts, but also after it has been waiting for a long time.

The solution must add the info in the code paths of the legacy range deleter (for pre-6.2.0 versions) and the new range deleter service.