Currently, the availability operations can have a random failure because of timing by doing a set-then-read operation. The updated availability may not be updated in all nodes.

Using an eventually block can fix the test, but maybe we want to wait all nodes to be updated before returning an OK response.

https://ci.infinispan.org/job/Infinispan/job/PR-10171/5/testReport/org.infinispan.rest.resources/CacheResourceV2Test/testCacheAvailability_security_false__protocol_HTTP_11__ssl_false_/