Ensure that the interpretation of bounding boxes is always half-open

[philippotto]

When a bounding box is defined with [0, 0, 0, 10, 10, 10], the position [10, 10, 10] should be outside of the bounding box. This interpretation was not consistent within the code base which I cleaned up with this PR. I tried to go through all the relevant code and double-check / fix it where necessary. Predominantly, the following two cases needed fixing:

• the dataset position view
• the rendered cube mesh (since threeJS renders the mesh always inclusively, I subtracted an epsilon there)

URL of deployed dev instance (used for testing):

• https://makebboxconsistent.webknossos.xyz

Steps to test:

• I did the following:
  • open a task with a bounding box (e.g., 0, 0, 0, 10, 10, 10)
  • initialize the api with window.webknossos.apiReady(3).then(api => window.api = api)
  • test the rendering with api.tracing.centerPositionAnimated([8, 5, z]) where z can be something like 9, 9.9, 10, 10.01 etc.
  • before this PR, being at z=10 and z=10.1 behaved differently (one showed the box, the other did not). with this pr, both positions act correctly (i.e., behave like one is outside of the bounding box)

Issues:

• fixes Bounding Box off-by-one errors #4684

---

• 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

[daniel-wer]

Works great, thanks for having a detailed look at this 👍