Leaked secondary index metadata files when crashing during index creation

When CC crash happens while a secondary index being created, its metadata files will continue to be in storage. On metadata recovery, this index entry with pending build indicator will be removed from the metadata catalog but the metadata files on storage will not be removed. While this won't cause a problem if the index is re-created since we will delete any existing metadata files first, those files might leak if the collection is dropped.

This can put the service is a restart loop due to not finding the primary index of the secondary during the node local recovery step.

The possible workarounds are:

1. Manually delete any leaked files from storage to all the node recovery to complete.
2. Failover the node facing the issue.