Explicitly create ES index

[di]

This fixes #1712 by explicitly creating the new Elasticsearch index when reindexing.

It seems like the behavior has changed since #1473: If we don't explicitly create the index, the default mapping that we get doesn't respect the keyword type for properties like classifier, which results in them being considered text instead, which results in them being tokenized and not matching exactly to their respective values.

To prevent the index_already_exists_exception in #1473 from returning, we can now tell create to block until all the shards become active. This should prevent the original (hypothesized) race condition between create, and parallel_bulk attempting to auto-create the index. (It's hard to say whether this really will prevent it as I still haven't been able to reproduce it in dev, but a stale index is better than one that doesn't work at all...)