Corrected compiler errors and warnings.

This have accumulated over the last dozen or so commits.
MODE-1802 - Fixed the handling of root projections for the FileSystemConnector
MODE-1802 - Updated as per code review, moved and added a test case to FileSystemConnectorTest.
MODE-1799 - Fixed the moving of nodes located under root.
MODE-1806 - Changed the way the projections are stored/removed so that the information is persisted each time into the repository. This way there shouldn't be any problems if the shutdown of the repository isn't orderly.
MODE-1791 - Added the "readonly" attribute to the connector hierarchy and implemented support for it in the base connector class. Also. updated the JSON schema to support it.
MODE-1791- Updated the read-only option for connectors by adding a WritableConnector base class which now contains the flag and by moving the read-only checks to the FederatedDocumentStore.
MODE-1810 - Added test cases which show that the problem cannot be reproduced
MODE-1805 Query system can be disabled in AS7 kit

Added ability to completely disable the query system (including the
generation/maintenance of indexes) in a repository in the AS7
subsystem. (The JSON repository configurations had this ability for
some time, but it could not be controlled in AS7.)

This adds a new "enable-queries" XML attribute on the "repository"
element in the subsystem configuration. This attributes defaults
to "true" and therefore is backward compatible. However, setting it
to "false" will completely disable the indexing system, although
any index storage and indexing configuration within a repository
configuration will remain as-is; it will simply not be used.
This means that the repository's indexes and query system can be
disabled (perhaps on a temporary basis) and then re-enabled without
having to completely reconfigure the index storage and indexing
parameters.

It was discovered that executing queries on a repository that had
its query system disabled resulted in a NPE, because the running
state did not have a RepositoryQueryManager instance. Rather than
deal with all of the potential NPEs, a new specialization of
the RepositoryQueryManager, called RepositoryDisabledQueryManager,
was added and is instantiated within the running state when queries
are disabled. This specialization essentially no-ops all of the
operations. The result is that queries will return no results
rather than throw an exception.

Additional warning messages are logged when the indexes are indeed
disabled, since this will rarely be done in production.

Several new tests were added, including unit tests (in
'modeshape-jcr') and integration tests for the AS7 subsystem.
MODE-1805 Minor cleanup of code per code review
MODE-1811 - Fixed the InfinispanBinaryStore not being able to load a class from modeshape-jcr, by making that class available in the AS 7.1.1 kit to the org.infinispan.main module.
MODE-1807 - Changed the order of steps in the node validation algorithm and updated the test case that caused this issue
MODE-1807 - Fixed the validation of residual child definitions
MODE-1816 The jcr:mixinTypes properties should not need to be first in the JSON requests

ModeShape should not expect that the "jcr:mixinTypes" property be
before the other properties in the JSON request coming from REST clients.
Some libraries will not allow clients to reliably choose the order.

Added a test case to verify this now works.
MODE-1804 - Corrected the schema and the Hibernate Search parameters for the jgroups-slave backend.
MODE-1813 - Implemeted an Arquillian based test using CDI and various deployment units.
MODE-1753 Merge two README files into one

Simple-minded merge:
 * copy the information from the README_COMMITTERS.txt file and insert
   into appropriate place in the README.md file
 * remove the README_COMMITTERS.txt file
MODE-1753 Removed "pardon our dust" from the 3.0 beta days

The top of the README.md file contained out-dated information from when
the 3.0 work had first moved to the master branch. Zapped it.
MODE-1816 REST v2 responses base property representations on number of values

The response should base the field value for a given property based upon
whether that JCR property is single-valued or multi-valued, not upon
the number of values. If multi-valued, then the field value should be
an array (even if there is just one item). Version 1 of the REST API
already works this way, but the version 2 was changed.

Note that it is still possible for property representations in
requests to use a single value (rather than an array) when setting
a multi-value to a single value, or the more conventional practice
of using an array to set a multi-valued array. The latter is obviously
required when setting the mutli-valued property to 0 or 2+ values.

Several of the expected results were incorrect and have been changed.
MODE-1809 Corrected the processing of set queries, including unions

The code was sorting and then removing duplicates in the tuples,
but during pre-processing and planning, the internal structure of the
tuples changed for certain kinds of queries (like unions with join)
to add in node location information as additional columns. The
removal of duplicates, however, was still incorrectly basing its
access of the tuple values upon the smaller/earlier tuple structure.
This cause various kinds of ClassCastExceptions.

Added a test case that replicated the originally reported problem,
which after the fix now passes.