Stream pipeline blocks if filterKeys() gets an empty set

When the set used for filtering via filterKeys(set) happens to be empty on a DistributedCacheStream, then the pipeline makes no progress and blocks the calling thread.

This "edge-case" should be normally handled by returning an empty/default/null value (whatever the pipeline defines).

The pull request contains a unit-test that proofs the point and should prevent a future regression.