MODE-1937 Corrected the Java sequencer's generated method nodes

Nodes representing methods were named with the method name and parameter
names, but this was changed to be closer to the standard Java signature
of method name and parameter types. This makes it possible to properly
support overloaded methods and constructors.

Several of the existing tests were modified to use overloaded
constructors and methods, and all pass with these changes. Note that
no changes in the node types were required, though the sequencer's
generated content is now slightly different (only in terms of the method
and constructor node names).
MODE-1937 Expanded method parameter information

Expanded the parameter information that is generated by the Java sequencer. The source file sequencer actually extracts a bit more information for each parameter, but at least the class file sequencer gets the parameters' types (just not the name or whether 'final'); the class file sequencer just generates parameter names dynamically.
MODE-1924 Changed AuthorizationProvider framework to always use absolute paths

Most of the time ModeShape was passing absolute paths to the AuthorizationProvider. However, in some places ModeShape passed relative paths, and this makes it very difficult for implementations to properly check permissions.

This behavior was changed so that ModeShape always passes absolute paths.
MODE-1924 Added AdvancedAuthorizationProvider

A new AdvancedAuthorizationProvider interface was added, where this new interface now provides access to the Session through a new context mechanism (which can be used in the future to add more parameters without breaking API compatibility).

The Session now simply does one extra instanceof check when attempting to determine the permissions.
MODE-1924 Renamed parameter to make it clear we pass the absolute path.
MODE-1934 - "De-activated" all Apache POI dependencies. No code was removed, so that if the underlying issue is fixed in a future version of POI, we should be able to easily bring it back.
MODE-1934 - Replaced TODOs with "See MODE-1934".
remove checks in AbstractBinaryStoreTest that were beyond the BinaryStore contract.
move start/shutdown methods from AbstractBinaryStore up to the BinaryStore interface
relax JcrRepository's binaryStore to support any BinaryStore impl
add BinaryStore#hasKey, for checking if a key is in the store
add collections helpers for concatenating iterators and iterables
Create a CompositeBinaryStore that:

- initializes any number of named BinaryStore instances
- appear as a vanilla BinaryStore to existing code
- allow consumers to offer a "StrategyHint" that MAY be used to
  determine what named BinaryStore to persist content to
- on retrieval, look for the BinaryKey in all named BinaryStores
relax requirement for composite binary stores to contain a default key; without a key, just use the first defined named store as the default
Add composite binary store support to EAP