Ingest Warnings, Fuseki 4.5, refactoring

Added ingestion warnings for missing, extra columns
Upgrade to Fuseki 4.5 support
Remove arangoDb

SPARQL gen cycles & minor improvements

First release of SPARQL generation of nodegroups containing cycles without MINUS or OPTIONAL
Next steps in CombineEntities
Fix bug in ?Node_type SPARQL generation
Re-hardcode version in all POM files

SPARQL gen fix and combineEntries REST endpoint

Fixed missing ?Node_type clause for a Node with no subtypes.
Added combine entries endpoint for entity resolution work.

Bug fixes to complex ranges and reports

Fixed:

• sparql generation on nodegroups with objects of complex ranges was missing the type constraint
• automatic nodegroup ingestion templates with objects of complex ranges had difficult-to-understand names: SecurityEntity->content_identifier_2 changed to SecurityEnitity->content_Port_identifier (complex range type is in the middle)
• SPARQLgraph was not protected from browser memory overflows from large queries in some sections of the report and construct queries on the query tab

Ingestion performance improvements

• Significant improvements in ingestion performance
• Complete the change-over to openapi-doc.
• Cleaner non-handling of SADL3 lists

Nodegroup generator fix for RACK v10.x

Nodegroup generator function was not matching the docs.
Make sure only the "main class" is createIfMissing and the rest are errorIfMissing.

For RACK 10.1

fix startup order and minor tweaks only

Few more fixes for testing before RACK release

Reverted nodegroup propertyItem.domainURI (incorrect and misleading new name) back to UriRelationship before it gets out. Bump nodegroup json to version 19.
Fixed disappearing report in SPARQLgraph when nodegroup store is accessed.

Bug fixes with complex ranges

Fixed and improved functionality for correcting invalid nodegroups in SPARQLgraph,
in particular when SemTK has detected a node that is a superclass of the current complex range.
SemTK used to allow this and no longer does.
So this helps users rectify the situation with a couple clicks.

Bug fixes with complex ranges

Fixed and improved functionality for correcting invalid nodegroups in SPARQLgraph,
in particular when SemTK has detected a node that is a superclass of the current complex range.
SemTK used to allow this and no longer does.
So this helps users rectify the situation with a couple clicks.