SERVER-135704ClosedWon't Fix

FP Safety 2/5: Fix no-op failpoint wait in reconfig test

h3. Background A failpoint's hit counter is process-wide and is never reset between tests in the same unit-test binary. So {{fpb->waitForTimesEntered(1)}} returns immediately if an _earlier_ test already hit it, and the wait silently does nothing. h3. What to do In {{replication_coordinator_impl_reconfig_test.cpp}}, test {{StepUpReconfigConcurrentWithForceHeartbeatReconfig}} has exactly this bug. An earlier test in the same binary hits {{blockHeartbeatReconfigFinish}}, so the wait passes immedi

Affected Versions
Versions known to exhibit this issue

No affected versions recorded.

Fixed Versions
Versions that include the fix

No fix available yet.

Components
Server components related to this issue

No components specified.

Labels
Tags and classification
bf-46466-postmortembf-postmortemrepo:10gen/mongo