Shards clear the CSRs for all the namespaces when recovering from a live rollback if the reported rolled-back namespaces or operations involve the auth shards DDLs.

SERVER-130703 prepared for any adverse impact by introducing a server parameter to disable CSR clearing. It also added some telemetry to ensure that we capture the issue in logs and FTDC.

We should address this long-term. There are several possible approaches, such as tracking exactly which namespaces could be impacted and only resetting CSR for them, vs proving and testing that we don't need to reset the CSR at all. We might need to do both to convince ourselves that it is safe to suggest the server parameter that we added as a mitigation.

This ticket addresses the long-term fix.