History should not be maintained for all access to revisions

By far the most used method for accessing revisions of a model is modelService.getLatestRevision. This is used in different parts of the code, not just when the user is actually accessing a model (e.g. search indexing and query), where history shouldnt be updated for that user. There is now an option in getLatestRevision not to update the history, which should be used in the code where appopriate.