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