Enforce magnifications via task type

[philippotto]

@youri-k Can you update the migration guide? A datastore update is probably not necessary, is it?

Additionally, to the mag enforcement, I also added an "active resolution" hint to the info tab. I think, this is quite useful (at least, it was for testing :)).

URL of deployed dev instance (used for testing):

• https://enforcemags.webknossos.xyz

Steps to test:

• edit a task type and check "enforce magnifications"
• fill min and max (you can also try to omit one value, as this should work, too)
• create a task for that task type
• trace the task and ensure that you can only zoom within that range

Issues:

• fixes Allow to enforce specific mag(s) for tasks #4075

---

• Updated changelog
• Updated migration guide if applicable
• Updated documentation if applicable
• [ ] Adapted wk-connect if datastore API changes
• Needs datastore update after deployment
• Ready for review

[fm3]

Backend LGTM (please update the PR number in evolution file + add migration guide entry)

[daniel-wer]

Code looks really good, the active resolution is very helpful! 👍

I started testing, but encountered an issue right away, so I first wanted to let you check that before continuing the testing:

• I created a task type with a min resolution of 4 and a max of 512
• I then created a task with that task type and opened said task
• The task loads at resolution 2-2-2 and I cannot zoom (neither in nor out)
• Tracing can be found at https://enforcemags.webknossos.xyz/annotations/Task/5ce40edb01000091019abcd0#567,216,331,0,1.000,1

[philippotto]

I started testing, but encountered an issue right away, so I first wanted to let you check that before continuing the testing:

• I created a task type with a min resolution of 4 and a max of 512
• I then created a task with that task type and opened said task
• The task loads at resolution 2-2-2 and I cannot zoom (neither in nor out)

Oh, very good catch! I fixed it now.

Also, do you notice any performance regressions when zooming? Locally, it appeared a bit laggier to me, but the reason might as well be that I used wk predominantly on deployed instances (where the code is optimized by compilation). In benchmarks, the code wasn't conspicuous.

[philippotto]

Backend LGTM (please update the PR number in evolution file + add migration guide entry)

@youri-k Could you do this? :)

[daniel-wer]

Works very well!
I didn't notice any performance regression when zooming, I'm also getting similar FPS during zooming on master and this branch :)