SES-1860 Only parse sparql tuple results if a handler is provider
SES-1860 : Push null checks down into SPARQLResultsSAXParser
SES-1860 : Add null check for boolean back in
SES-1860 : Patch testsuites to test for no handler and a parse exception
when passing a tuple results set through a boolean interface method, to
avoid a regression with the previous behaviour on the deprecated parse
method.

Workaround, and the reason the tests are not failing now, is to use
QueryResultIO.parse which internally sets up a handler to avoid the NPE
and throws the expected exception in the tuple case.
SES-1860 : Patch SPARQLXMLParsers to fail if they receive unexpected
results through the old deprecated methods, and to work if they do not
receive a handler
SES-1860 : Patch SPARQL Results JSON parser to throw exceptions for
deprecated methods to provide backwards compatibility when no handlers
are set, and when tuple results are sent through the deprecated boolean
parse method
SES-1860 : Add tests for passing boolean results through tuple parsers

Also add tests for no handler to ensure that parsers all work without
explicit handlers, even if they are only effectively verifiers in this
case if they cannot transmit information back to the caller
SES-1860 : Make BinaryQueryResultParser work without a handler setup
SES-1860 : Make SPARQL Results TSV Parser work without a handler

Also correct the implementation to call endQueryResult which was not
previously being called.
SES-1860 : Make SPARQLResultsSAXParser fail if it finds a boolean result

Previously it silently ignored it, even though the boolean results are
supposed to be parsed through SPARQLBooleanSAXParser. Now that we know
what to expect for the deprecated methods, we need to fail if we find
boolean results in the SPARQL Results XML tuple parser
Merged in SES-1860 (pull request #159)

SES-1860 SES-1868 SES-1869 : Query Result Parsers do not support null handlers uniformly