SERVER-133231ClosedFixed
Fix read_pref_cmd.js to wait for replica set before running profile
BF-45277 — read_pref_cmd.js: profile entry lost on a lagged secondary after dropDatabase/re-create Mechanism. The test loops: setUp() → testCursorReadPreference() / testConnReadPreference() → tearDown(). tearDown() drops read_pref_cmd and waits for replication; the next setUp() re-creates the database via enableSharding + shardCollection on the primary. Those are majority writes, so in a 3-node set they return as soon as the primary and one secondary ack — the third node can still be behind.