MODE-1873 Corrected how subquery results are converted to criteria

When a subquery selected a pseudo-column (like 'jcr:path'), the query
result contained Path instances. These values could not be successfully
used in criteria, since they were not converted to the correct value type
expected in the dependent query. Since only pseudo-columns were a problem
(and really only the 'jcr:path' and 'jcr:name' pseud-columns since they
return Path and Name values, respectively), the code that grabs the
subquery results was modified to convert these non-standard types
to strings.

A test case was added to the text sequencer test case, since that was
the best place for replicating the problem query (which used the
'mode:derivedFrom' property created during the sequencing operation).
However, once the problem was identified, I created a simple test
case within the JcrQueryManagerTests.
Corrected compiler warning
MODE-1851 Added test case to show 3-way joins do work

Added a test case that uses the S-RAMP node type design and checks
that 3-way joins can be used to 'resolve' S-RAMP relationships.
MODE-1888 Added warnings to queries

The ModeShape-specific query API not includes warnings on QueryResult objects. ModeShape will include warnings in a number of cases, including when column names are misspelled (via common patterns), or when columns is a better match with a different selector.

Several new test cases were added to verify the behavior.
Moved the AS7 subsystem and distributions modules back in the main build list, so that a simple `mvn clean install` will build the AS7/EAP dist by default. For the rest of the profiles (assembly, integration etc) Maven will resolve the correct order (based on dependencies) when they are activated.
MODE-1872 - Changed the default configuration so that re-indexing is done asynchronously. This exposed the need to be able to shut down the re-indexing process when a repository is shutdown.
MODE-1872 - Fixed lazy workspace creation, so that it's atomic.
MODE-1876 Removed expensive ops to allow reindexing large repositories

Recently the reindexing operations were changed so that upon "IF_MISSING"
any already-indexed node would be skipped. However, this was not really
the intention of the "IF_MISSING" option, and the logic to determine which
nodes were already indexed was quite expensive. Therefore, the logic
was changed to reindex the entire repository's content whenever the
indexes were missing (e.g., either empty or not yet created).
Corrected compiler warnings
MODE-1876 Corrected the logic that determines if indexes are empty

Because the JcrRepository is trying to determine if the indexes are empty
after the system nodes have already been created, the query components
have to determine when the indexes are first set up whether there is
already content in the persisted indexes (e.g., the files on the directory).
MODE-1894 - When indexes are being updated, the map of computed properties should be passed down, instead of both the old the new values.
MODE-1887: Merging workspace
MODE-1887: Remove commented out lines
MODE-1887 Removed commented out criteria in if-check
MODE-1841 - Added a test case which uses a configuration similar to the one described in the issue and stores binary values.
MODE-1895- Fixed Solr and Orm modules from the "patched" hibernate search distribution
MODE-1896 Deprecated the "transactionManagerLookup" field

This field in repository configuration files has not been used for some
time, but at the time it was not properly documented in the schema as
being "deprecated". This has been done, and any use of this field in
our test configurations have been removed.

Note that the RepositoryConfiguration constructors now log warning messages
when this or any other deprecated fields are used.
MODE-1883 - Updated the restore method, so that a meaningful exception is thrown if a removed node is restored. Also, re-activated an ignored test from the ModeShapeTckTest class.
MODE-1897 - Updated clustering tests with a new test using JGroups for
clustering Hibernate Search. This should hopefully prove that it's
possible to cluster indexes using master/slave configurations. Also,
update the JSON schema so that the "channelConfiguration" attribute is
optional, because Hibernate Search provides one out-of-the-box.
MODE-1829 - Fixed parsing of leading wildcards