In SERVER-125005, support was added for resuming a primary-driven index build even when the persisted resume state is missing, resuming the index build in the kInitialized phase. We should add jstests to cover:
(1) resuming a primary-driven index build that gets interrupted in the kInitialized before the resume state document is written,
(2) resuming a primary-driven index build that gets interrupted in later phases, but is missing the resume state document.

While the scenario for (2) should not be possible under normal circumstances, it will be good test coverage to include this and ensure expected functionality - I.e. that the index build is resumed from scratch in the kInitialized phase.