WIP Reserve annotation ids via postgres, add collaborationMode

[fm3]

URL of deployed dev instance (used for testing):

• https://___.webknossos.xyz

Steps to test:

• abc

TODOs:

• backend

  • collaborationMode
  • reserveIds + reservedIds routes
  • schema
  • scan in tracingstore (caveat: segment ids in fallback layer case not supported yet)
  • reserve queries for postgres
  • free ids when annotation colalborationMode is switched back away from Concurrent
  • foreign key constraints
  • mutex
  • evolutions
  • test

• frontend

  • collaborationMode
  • reserve ids

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

[fm3]

@philippotto The backend functionality is done, but I could only do rudimentary tests without a corresponding frontend. Summary:

• changed the othersMayEdit property to collaborationMode, update route is api/annotations/:typ/:id/collaborationMode.
• new route GET api/annotations/:id/reservedIds?tracingId=x&domain=y (domains are Segment, SegmentGroup, Tree, Node, TreeGroup, BoundingBox)
• new route POST api/annotations/:id/reserveIds) expects json body:

    domain: AnnotationIdDomain,
    tracingId: String,
    numberOfIdsToReserve: Int,
    idsToRelease: Array[Long]

returns json array of newly reserved ids.

Note that the segment domain is only partially supported. It will fail for annotations with fallback segmentation layer, as discussed previously.

CI currently fails because the frontend types don’t yet understand collaborationMode.

Let me know if you need anything else!