Additional axes bounds as semi-open interval

[fm3]

We decided to change the format for additionalAxes in the datasource-properties: the upper bound is now exclusive. That is now also used for volume annotations and in the NML format.

Steps to test:

• download nd test dataset from notion, put in your binaryData dir
• run migration script, should update the json (bounds should now be [0,18])
• open datast in wk, should be able to load data from t=0 to (inclusive) t=17
• create annotation for the ND datast, download, reupload, should look the same, have correct bounds

TODOs:

• Naming
  • bounds array with two elements
  • in NML: start, end
• Backend
  • NGFF explore
  • data loading
  • volume download
    • Also fix mag regex in volume upload (unrelated bug)
• Frontend
  • slider
  • data loading
• Migration
  • python script to migrate existing datasource-properties.jsons, traversing binaryData directory
  • migrate volume tracings? Decided not to (there aren’t any on our wk instances)
• Libs
  • Make sure this works with Reading nd datasets webknossos-libs#966

Issues:

• fixes Additional axis limits should be semi-open interval #7515

---

• Updated changelog
• Updated migration guide if applicable
• Considered common edge cases
• Needs datastore update after deployment

[fm3]

@markbader could you comment if this works with scalableminds/webknossos-libs#966 or if you need anything else from us to adapt it? :)

[philippotto]

front-end also looks good to me 👍

I guess it's not worth it to make the migration idempotent?

[fm3]

I guess it's not worth it to make the migration idempotent?

Shouldn’t think so. If it does fail, we have the .bak files. There aren’t hundreds of nd datasets in the first place

[markbader]

@fm3 For wklibs these changes are fine, and I currently don't need anything else to be adapted. Thanks!