jstests/noPassthrough/index_builds/index_build_restart_secondary.js fails with a data corruption issue. Cursory inspection + thinking about how secondaries handle restart, I think this may come from secondaries trying to boot up their own index builds / clearing state they shouldn't. We should be able to just add a gate or two in the startup logic to ensure secondaries that restart can cleanly continue to replicate index build related oplog entries instead of trying to take over or perform legacy behavior