Timeout/Cancel Querycomputation

Our evaluations revealed cases/ontologies (e.g. a modified opengalen ontology see https://git-ainf.aau.at/interactive-KB-debugging/debugger/tree/Evaluation_Fall2016/owl-plugin/src/evaluation/resources/ontologies) where even the heuristic query computatation method is too expensive when it comes into it's enrichment/optimization phase (expensive means that the solver calls necessary for enrichment/optimization can last many days).

A timeout could solve this problem by stopping the search for enriched/optimized queries after a timeout of default 60 seconds occurs. The user could still get a query from the canonical query which is computed independently from the solver.