Add option to disable tracking "remote executions".

[Aklakan]

LSQ can actually be used for benchmarking any set of sparql queries - such as ones produced by a query generator.
Such queries do not correspond to a log file and thus do not have remote executions.

Right now one can RDFize a file containing multiline sparql queries with:

lsq rx rdfize -m sparql multi-line-sparql-queries.rq

As a secondary issue, for some reason explicit -m sparql is needed for multiline sparql queries because query format auto-detection (aka probing) yields the format sparql2 which is the 'sparql query per line' (with encoded newlines) format.

However, in such cases, the output contains needless remoteExec resources:

<http://lsq.aksw.org/lsqQuery-0JZqkFLBIZX934e78cAKZTqP9UoOoOVGE6T0wh1fC48.AA.AA.s.GdjNBA.AA.AA.AA.AA.AA.qeAbhAAA.AA.AA.AA.HM5Tgg> {
    <http://lsq.aksw.org/remoteExec-_243>
            <http://lsq.aksw.org/vocab#endpoint>  <urn:grid-bench:512x512x16r> ;
            <http://lsq.aksw.org/vocab#query>  "SELECT ..." .
    <http://lsq.aksw.org/lsqQuery-0JZqkFLBIZX934e78cAKZTqP9UoOoOVGE6T0wh1fC48.AA.AA.s.GdjNBA.AA.AA.AA.AA.AA.qeAbhAAA.AA.AA.AA.HM5Tgg>
            <http://lsq.aksw.org/vocab#text>  "SELECT ..." ;
            <http://lsq.aksw.org/vocab#hasRemoteExec>  <http://lsq.aksw.org/remoteExec-_243> ;
}

In the benchmark setting, rather than expressing that a query was executed on a remote endpoint, the semantics is that a query was part of a query mix.

The triple

<http://lsq.aksw.org/remoteExec-_243> <http://lsq.aksw.org/vocab#endpoint>  <urn:grid-bench:512x512x16r> .

is not too bad but it should be something like:

<http://lsq.aksw.org/membership-243> :in <urn:grid-bench:512x512x16r> .

So LSQ needs a flag to switch modes.