Add operation on ShuffleSharding to filter READONLY ingesters

[danielblando]

What this PR does:
We found an issue when a tenant has ingestion_tenant_shard_size lower than the number of ACTIVE ingesters or high number of READONLY ingesters when testing the new status of READONLY.

Eg:
Failed Push
Lets assume we have a ring with
10 ACTIVE ingesters
50 READONLY ingesters
tenantA ingestion_tenant_shard_size of 20

The current subRing of this tenant can be created with only READONLY ingesters. In this case, DoBatch will fail as there will be no health ingesters to send data.

Early throttle
Lets assume we have a ring with
80 ACTIVE ingesters
20 READONLY ingesters
tenantA ingestion_tenant_shard_size of 20

The current subRing can be created as a mix of ACTIVE and READONLY ingesters. This will cause a subRing of size 20 but only 15 ACTIVE ingesters supposedly. The localLimit for each ingesters will be calculated over 20 as the shard size but only 15 ingester are receiving all data. The new scenario will create a subRing over just the 80 ACTIVE ingesters.

This PR introduce a ShuffleShard ring filter by operation. We then create a new WriteShard operation to filter out READONLY ingesters of shuffleSharding subRings. The cache for sharding will be clean as usual when the ring changes or a READONLY status changes in the ring.

In the first case, we will create a subRing with only 10 ACTIVE ingesters avoiding causing 5xx on Push
The last scenario, we will create a subRing taking in consideration just the 80 ACTIVE ingesters avoiding READONLY ingester s to miss count the limit.

Checklist

• Tests updated
• Documentation added
• CHANGELOG.md updated - the order of entries should be [CHANGE], [FEATURE], [ENHANCEMENT], [BUGFIX]