Near cache with invalidation fails to start in Spring Boot

We included more checks and restricted the installation of the listener when the conversion of types between the client and server is not possible. See ISPN-15197.

In conjunction with a Spring Boot application, all the caches defined in the cache manager are loaded during the bean initialization. This installs the listener when the near cache has a mode of INVALIDATED. Since the default marshaller configured by the `InfinispanRemoteAutoConfiguration` is the `JavaSerializationMarshaller`, some issues can happen with internal caches. For example, it loads the `respCache` with keys of type `octet-stream`.

Since we have more restrictions when installing the listener, the application fails to start, even though it is not a user installing a custom cache.