MODE-1608 - Fixed the code for Except and Intersect components when the tuples iterators have no more results

Also added test case. These were essentially the same changes for MODE-1595 (for 2.x).
MODE-1594 Added test case for JCR-SQL2 queries that were problematic in 2.x
Corrected sandbox POM
MODE-1600 Decreased runtime of ISPN BinaryStore tests
MODE-1606 InfinispanUtil.getAllKeys for backup
MODE-1603
MODE-1095 Fix support for ORDER BY using a column that isn't in the SELECT

The query framework was changed to ensure all columns used in the ORDER BY clauses
are automatically included in the results. Because the query processing engine
requires the columns to be in the (intermediate/internal) results, including the
columns in the user's result set does not make the query system less efficient.
(In fact, changing the result set to contain/expose only those columns included
in the SELECT clause would actually require additional resources and could be
potentially less efficient.)

This change implements the functionality by adding a new optimizer rule that
rewrites part of the query plan. In particular, the new rule looks for SORT query
plan nodes, processes the Ordering instances to extract the property references,
and adds corresponding columns to all the appropriate PROJECT nodes that are below
the SORT node.

This change altered the query plans for queries with orderings, so the expected
results needed to be changed in several test cases.
MODE-1599 Corrected how result columns are qualified with table name for QOM queries

The org.apache.jackrabbit.test.api.query.qom.ColumnTest#testExpandColumnsForNodeType() TCK test runs
queries in both the Query Object Model (QOM) and JCR-SQL2 languages, and expects that the result set
columns for both are named like "selectorName.propertyName", even for queries such as
"SELECT s.* FROM [nt:unstructured] AS s".

The JCR-SQL2 query result set columns were named correctly, since we set the qualifyExpandedColumnNames'
field in the PlanHints for this language. However, the hints for the queries created programmatically
using the JCR-QOM QueryObjectModelFactory interface were not being set in the same way. This
change corrects that and no longer ignores the ColumnTest#testExpandColumnsForNodeType() TCK test.
Merge branch 'mode-1095' of git://github.com/rhauch/modeshape into rhauch-mode-1095
Merge branch 'mode-1599' of git://github.com/rhauch/modeshape into rhauch-mode-1599
MODE-1614 - Fixed various usages of ValueFormatException
MODE-1338 Convert Teiid sequencer to the new 3.0 sequencing API
Commiting to remote fork of all work done so far. I am upgrading OS X version so want to make sure I have a backup.
MODE-1338 Convert Teiid sequencer to the new 3.0 sequencing API
MODE-1369 Update Teiid VDB sequencer to look for new contents in vdb.xml
Both the Teiid VDB sequencer and the Teiid model sequencer have been converted to the 3.0 API. Also the VDB sequencer has been updated
to sequence the latest vdb.xml file. Still need to change top-level POM to move this project out of the legacy profile. Also, the
model sequencer still has work associated with references and types which will affect the model object handlers and the sequencer.
MODE-1338 Convert Teiid sequencer to the new 3.0 sequencing API
Finished sequencer implementation. Mostly work done on processing model objects and resolving unresolved references.
MODE-1338 Convert Teiid sequencer to the new 3.0 sequencing API
Changed the top-level POM file to move the Teiid sequencer module outside of the 'legacy' profile.
MODE-1338 Convert Teiid sequencer to the new 3.0 sequencing API
Remove logical relationships from CND and model object handlers. Increased sequencer test time before failing.
MODE-1338 Convert Teiid sequencer to the new 3.0 sequencing API
Fixed a bug in the assert of a model object handler.
MODE-1338 Added Teiid Sequencer to JBoss AS kit and distributions
MODE-1617 - Fixed the lack of persistence for created/deleted workspaces
MODE-1338 - Enforced the "test" scope for the slf4j and log4j dependencies