Indexing write.lock remains even after a restart

When the indexing write.lock isn't removed (e.g. if 100% disk usage is reached during indexing) this can create a number of problems including being unable to delete a space or see updates on the dashboard (see CONF-22981).

We should delete this if it's present on startup.