ClientClusterExpirationEventsTest.testSimpleExpired random failures

http://ci.infinispan.org/job/Infinispan/job/PR-5284/9/testReport/junit/org.infinispan.client.hotrod.event/ClientClusterExpirationEventsTest/testSimpleExpired/ shows the failure.

What happens is a RemoveExpired command from the testFilteringInCluster test can be seen in a later test. This is because testFilteringInCluster does not wait for the expiration event to be sent, because it is filtered out, so there is no way to tell when it is actually invoked.

The easiest way to fix may be to just add another listener that waits for the entry to expire, thus making sure the event doesn't occur on another test.