Stronger isolation between modules needing Infinispan Core and those needing Lucene

The WildFly module 'org.infinispan:main' is exporting Infinispan Query as a convenience for users, but this in turn exposes Hibernate Search and Apache Lucene, which are often not desirable, especially to other internal modules which simply need access to the primary Infinispan integration contracts.

I will propose a split of the modules which maintains the convenience for end users but avoids bloated classloaders.