Indexes from different caches are mixed-up in server mode

When configuring multiple caches as indexed in the server, they'll effectively use the same index at runtime since Infinispan internally uses a single entity ProtobufValueWrapper to store the values in the index.

This can cause issues with two caches having the same key stepping in each other's toes. Example, when doing:

remoteCache1.put(1, entity1)
remoteCache2.put(1, entity2)

The second call will replace the first indexed entry since the key is identical and the internal index named "org.infinispan.query.remote.impl.indexing.ProtobufValueWrapper" is shared.