Fix unwanted group expansions

[daniel-wer]

This fixes a bug which was introduced in #4897.

The finishSearchCallback is not only called if the parent groups of the found node are expanded, but also when the tree data changes (where the parent groups of the found node are not expanded). I implemented a fix for that by checking for each element on the path whether it was actually expanded, but that was rather complicated. Therefore, I solved this issue in a more general way by updating the expandedGroupIds list whenever the onChange handler of the sortable-tree is called because the tree data changed. This way the two structures are always in sync. I think this solution is much less error-prone and the performance impact should be negligible.

URL of deployed dev instance (used for testing):

• https://___.webknossos.xyz

Steps to test:

• The bug could be triggered as follows. Create a tracing with this structure:

  • groupA
    • tree1
  • groupB
    • tree2

• Activate tree1 and then collapse groupA. Now change the visibility of groupB or tree2.

• On master this would expand groupA again, which should no longer happen on this branch.

• Also check whether group expansion, toggling of all sub groups works as before.

---

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

[philippotto]

Cool! Works for me and looks a lot cleaner :) Let's hope the performance also turns out to be alright.