SERVER-139302ClosedFixed
Fastcount can drift on index build attempts collection on clean shutdown
If a _clean_ shutdown and restart rolls back a commitIndexBuild or abortIndexBuild the sizeStorer's count for local.config.indexBuilds is left 1 higher than it should be. At the time of shutdown, (assuming no other index builds) the collection is empty and the count is correctly 0. On startup, the index build is restarted due to that the commit/abort has been rolled back, which creates a ledger document and sets the count to 1. Oplog replay then reapplies the commit/abort, which deletes the docu