Feature/#159 annotations performance

Feature

Summary

This MR provides a solution for making the annotations more performant.

Instead of determining the relevant annotations items on the fly they are now stored in one file per page. This file is stored in /db/data/textgrid/json and updated by a database trigger each time the respective file gets updated, too.

This MR also contains some fixes in the editorial annotations for that have been discovered during testing the main feature of this branch.

Compliance to “Definition of Done”

• Unit tests passed
• Code reviewed
• Product Owner accepts the User Story

Documentation

• I updated the README (if applicable)
• I provided my functions with appropriate documentation
• I updated existing documentation

Tests

Are we able to test this new feature?

• Yes, everything can be done via unit tests.
• Yes, you can test by following these steps:

1. build the database locally
2. publish the Arabic and Karshuni collection to your local database
3. after having published them each page of each TEI document has a *.json containing the relevant annotation items in /db/data/textgrid/json.

Changelog

• I added a statement to the CHANGELOG.

Version number

• I bumped the version number in build.properties.

Closes

Closes #159 (closed).

Logs and Screenshots

/cc Mathias Göbel, Frank Schneider, Michelle Weidling