Can't replace a file in a single index job

### Issues
- File deletions and inserts happen in the reverse order, meaning new files can never know if they are replacing one in the same transaction
- This means moving a file and immediately scanning the move is likely to lose metadata information
- This was mitigated by removing the file, indexing, and readding the file and indexing again in 4 steps rather than 2