[BUG] Fix tests relying on wait_for_active_shards

[monusingh-1]

What is the bug?
wait_for_active_shards setting will not allow the index to close as more than 1 shard will not be active.
This causes the test to fail.

{"acknowledged":false,"shards_acknowledged":false,"indices":{"remote-index":{"closed":false,"failedShards":{"0":{"failures":[{"shard":0,"index":"remote-index","status":"SERVICE_UNAVAILABLE","reason":{"type":"unavailable_shards_exception","reason":"[remote-index][0] Not enough active copies to meet shard count of [2] (have 1, needed 2). Timeout: [30s], request: [verify shard [remote-index][0] before close with block 4,RRq3_-4RRi2uSs03x15Odw,index preparing to close. Reopen the index to allow writes again or retry closing the index to fully close the index., blocks WRITE]"}}]}}}}}%

[monusingh-1]

Fixed in #1091