Avoid that an unsaved state is shown when loading an annotation

[daniel-wer]

The functionality to "hide" some changes to the 3d viewport from time tracking (so from the save queue) was already there, but in this spot the boolean was not set. Since this piece of code is only triggered when changing the size of the viewports or when changing the zoom (which triggers an update action, anyways) or clipping distance, it's not relevant for time tracking.

I've also added that the save queue entries won't be compressed in the dev environment. This eases debugging and one cannot forget to revert the change before committing any longer. Let me know if you think that's an issue.

URL of deployed dev instance (used for testing):

• https://___.webknossos.xyz

Steps to test:

• Open or create an annotation. The save button shouldn't show any unsaved changes.
• Move, zoom or rotate in the 3D viewport -> There should be unsaved changes.
• Other changes should still show unsaved changes and be saved across reloads.

Issues:

• fixes Creating new annotation immediately leads to "unsaved" state #5882

---

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

• Updated changelog
• Considered common edge cases

[philippotto]

Awesome, works great :)

I agree with your compress suggestion 👍 One could even think about having a variable exposed in window (or GET parameter) so that we can switch the behavior on prod instances ad-hoc. However, I think, this is something for a future PR (I have some other ideas for such debug-related use cases).