Exception message should be clearer when ModeShape is looking for cache with wrong name

A very common mistake when configuring ModeShape's JSON and Infinispan's XML files is to not match the cache names. For example, when ModeShape looks for a cache named in the configuration file, it always finds one since the Infinispan configuration really is defining default configurations for caches (even those that are unnamed). The problem is that (usually) the resulting cache will not have transactions enabled, and this is the exception:

javax.jcr.RepositoryException: org.modeshape.jcr.ConfigurationException: The 'sramp' repository cannot be started because transactions are not enabled. Please check your configuration.

That's fine, but this exception message should be improved to also suggest ensuring that the name in the repository configuration matches that of a cache in the Infinispan XML file. It should also probably say that the cache must have transactions enabled.