Prototype qlever

How would we implement qlever in scheduler and ec_utils
* Qlver
* [Control](https://github.com/ad-freiburg/qlever-control)
* [Control files](https://github.com/ad-freiburg/qlever-control/tree/main/src/qlever/Qleverfiles)
* [Ec_utils manage graph] -- **abstract methods now in place for blazegraph and graphdb**. (https://github.com/earthcube/earthcube_utilities/blob/main/earthcube_utilities/src/ec/graph/manageGraph.py)
* If they don't match qulevel, then rethink the abstract methods
* [Schedule](https://github.com/earthcube/scheduler/blob/dev/dagster/implnets/workflows/ingest/ingest/resources/graph.py)
* Make more abstract
* Think about [how to better abstract/implment] -- done possibly with a configuration name (https://github.com/earthcube/scheduler/blob/e8b61a7c272d7fad5b86f1dc17c8a1c49c0be7ff/dagster/implnets/workflows/ingest/ingest/__init__.py#L144) the __init__ that houses the resource configuration

----
initial steps
* setup a docker container
* setup a manually loaded from release file prototype community with a qleverconfiguration file
* one small set
* large set (include r2r)
* manually run SPARQL:
* query that [builds the summary](https://github.com/earthcube/earthcube_utilities/blob/main/earthcube_utilities/src/ec/graph/sparql_files/all_summary_query.sparql)
* an original pre-summary sqarql query to test performance these may be found [here ] (https://github.com/earthcube/facetsearch/blob/vue2/client/src/sparql_blaze/ ) the full text part will need to be redone
* might customize the build the summary query with the full text search
* graph reports [listed here](https://github.com/earthcube/earthcube_utilities/blob/3206f16f45e5575179a411495e458dec66e9ecc4/earthcube_utilities/src/ec/reporting/report.py#L175) in the graph/sparql path
* configure a facet search pointing at the endpoints, test

What are the evaluation criteria?
* does it perform well?
* fast summary query?
* original query that does not use the summary
* can we create multiple 'namespaces' like blazegraph, or how do we handle this
* can we create qlever load configurations from the tenant configuration (or what do we have to do)