libtracker-data: Update nao:lastModified after creating new database
It used to happen only right after ontology checks, which left branch new databases with an unset ontology modification date. This really didn't have ill effects, on the second run ontologies would be checked, but no real change would happen except the nao:lastModified change. Still better to do it at once, instead of waiting for the next run.
Showing with 43 additions and 14 deletions