This is given as user data to the TrackerDBManager and underlying ifaces
for the "tracker_triples" virtual table, so must remain stable along its
lifetime.

The only offender here are the paths that load the ontology from the
cache GVDB file, make tracker_ontologies_load_gvdb() take a
TrackerOntologies to load the file into, instead of having it return
a new one.