SERVER-108378ClosedFixed
Better cache lookup for `ReadConcern`
h2. Problem On a 100% findById workload, {{_extractReadConcern}} is called on every query via the primary dispatch path: {{ServiceEntryPointShardRole::handleRequest}} → {{ExecCommandDatabase::_extractReadConcern}} → {{ReadWriteConcernDefaults::getDefault}} → {{ReadThroughCache::acquire}} → {{pthread_mutex_lock}}. In the common case — no cluster-wide read concern (CWRC) configured, no explicit read concern on the request, no transaction, external client — the function performs substantial work