If a user declares `@EnableCaching` in their Spring application while using this add-on, the Infinispan Starter will create a new reference of `SpringRemoteCacheManager`.

This instance will clash with the user's defined `CacheManager`, ending in an exception during the application bootstrap.

Ideally, we should either block this bean creation, implement a CacheResolver, or document how users should deal with this scenario. They can either use Infinispan as their application data cache or they can mark their own CacheManager as Primary to use theirs. 

See: https://infinispan.org/docs/dev/titles/spring_boot/starter.html#enabling-spring-cache_remote