WIP cache more properties in annotation layer postgres table

[fm3]

URL of deployed dev instance (used for testing):

• https://___.webknossos.xyz

Steps to test:

• abc

TODOs:

• [x] evolution
• [x] determine properties map from AnnotationWithTracings object
• [x] on wk side, ingest them, write to postgres
• [ ] should it be sent by the frontend instead, to get it eagerly, not just on next reload?
• [ ] migration to fill this out for all existing tracings?
  • [ ] skip flushing in this case?
  • [ ] should this run indefinitely?
• [ ] in the future if we add properties, how do we know which are known?
• [ ] cleanup

Issues:

• fixes #

---

(Please delete unneeded items, merge only when none are left open)

• [ ] Added changelog entry (create a $PR_NUMBER.md file in unreleased_changes or use ./tools/create-changelog-entry.py)
• [ ] Added migration guide entry if applicable (edit the same file as for the changelog)
• [ ] Updated documentation if applicable
• [ ] Adapted wk-libs python client if relevant API parts change
• [ ] Removed dev-only changes like prints and application.conf edits
• [ ] Considered common edge cases
• [ ] Needs datastore update after deployment