MODE-1762 Added code to ensure the sequencers always close the Binary's stream

Our Binary values always return a stream that closes itself when fully-read.
However, if any of the sequencers do not read the entire stream (e.g.,
intentionally or if they experience an exception while processing),
the stream might not be closed.

These changes ensure that the stream is always closed. All sequencer
implementations where checked, and only those that were not always
closing the stream in a finally block were modified/corrected.

All tests pass with these changes.
MODE-1761 Added debug and trace logging to sequencing operations

Added debug logging for 'org.modeshape.jcr.sequencing' that outputs
the initialization of each sequencer (with valid path expressions)
and each invocation of a sequencer.

Added more trace logging for 'org.modeshape.jcr.sequencing' that
outputs very details messages describing the various activities
(and exit points) of sequencing.

Note that unconventional log names were used to make it easier
to enable and disale all logging for sequencing.
MODE-1768 Added checks to include only existing and readable files as child nodes
MODE-1767 Added logic to simplify MIME Type handling

When a session is saved, it now looks for nodes that are of type
'nt:resource' (including when the node's primary type is a subtype)
and checks whether the 'jcr:mimeType' property is set. If it is not
and there is a 'jcr:data' property with a single BINARY value, then
the session attempts to obtain the MIME type from the Binary value
and set the 'jcr:mimeType' property. (Note that name of the
'nt:resource' node's parent, if there is one, is supplied to the
'getMimeType(...)' method to hopefully get the most accurate MIME
type for the node.)

This is useful because applications should be able to access the
MIME type for 'nt:resource' nodes (e.g., the 'jcr:content' child
of 'nt:file' nodes is often of type 'nt:resource') without having
to cast to a ModeShape-specific interface.

Because the MIME types are computed asynchronously as soon as the
Binary value is created (and thus before it is set on a specific
value), the determination of the MIME type will hopefully have
completed before 'Session.save()' even tries to get the value.

Also, the 'jcr:mimeType' property is an optional property on
'nt:resource'. So whenever possible, client applications should
set this property where possible. In such situations, there is
no additional overhead to the 'Session.save()' call.
MODE-1767 Added unit tests

Added four unit tests that verify the behavior of the automatic setting of the
'jcr:mimeType' property only on nodes of type 'nt:resource'.
MODE-1773 Made the projection expressions more general
MODE-1765 - Updated the AS7 distributions so that there's a dedicated one for integration-testing (which overrides the default one). The default AS7 distribution has been "cleaned up" and is now testing only during the "assembly" phase via a separate Maven module.
MODE-1760 Add explicit dependency for jboss-connector-api_1.6_spec
MODE-1760 Rearranged JCA dependencies
MODE-1772 Added test case to replicate the problem of creating nodes under projections
MODE-1772 Ignored replication test case

This is to be un-ignored when fixing the issue.
MODE-1770 Added PESSIMISTIC locking to the default, in-memory Infinispan configuration

The LocalEnvironment class and its createDefaultConfiguration() method
are used to create the default cache configurations for in-memory content.
This method does set up the transactional behavior, but does not set
the locking. Therefore, I think it is prudent to add code to this
method that sets up the LockingMode of PESSIMISTIC.

Verified that this has no negative effect on the tests.
MODE-1775 Improved the Session.getNodeByIdentifier() method

Improved the method used to look up nodes by string identifier. The
logic is now:

- If the identifier is a full node key, use it to look up the node
with that key; if not found, continue
- Look for the node in the workspace content, using a key that is
the same as the root node key except with the supplied identifier part;
if not found, continue
- Look for the node in the system workspace content, using a key
that is the same as the "/jcr:system" node except with the supplied
identifier part; if not found, throw the ItemNotFoundException from
step #2.

The method previously just did steps 1 and 2, so step 3 is what was
added. A new test case verifies that the change fixes the original
problem
MODE-1772 - Updated the connector SPI and the document store so that a writable connector can generate its own ids when new nodes are created.
Added overlays folder to .gitignore.
MODE-1774 Changed the problematic error log message to debug

Also changed the verbage to not sound so dire, since the repository
might not yet have been started.
MODE-1561 - Added the writeLimit parameter to the TikaTextExtractor.
Fixed Maven parent version of  the modeshape-jbossas-kit-tests module.
MODE-1783 - Fixed the lack of constraint validation when updating properties