Add UI for segment statistics (volume and bbox)

[dieknolle3333]

Steps to test:

for a single segment

• Go to annotation without fallback layer
• Brush a segment
• Right-click the segment and read its volume
• Copy the size to clipboard

in segments tab

• right-click on any group to open its context menu
• select Show Segment Statistics
• view table and download CSV

TODOs:

• handle update of size by having context menu visibility as dependency
• improve icon
• implement reload button with tooltip "update this statistic", that saves the annotation
• mock-up of size in segment tab
• get size of all successor segments of a group recursively, not only direct children
• add spinner while segment statistics are loading
• make sure its the latest size, so that annotation was saved recently when the modal is opened
• show bounding box in columns and in CSV after the route was built
• improve naming of CSV
• get group name
• include bounding box info in segment context menu
• make group actions recursive
• check whether size in nm³ and bouding boxes are actually correct
• maybe improve how root group is defined by not just checking for null

Issues:

• fixes Use segment statistics routes in frontend #7145
• contributes to Improve performance of the segment list tab #7319

---

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

• Updated changelog
• Removed dev-only changes like prints and application.conf edits
• Considered common edge cases

[fm3]

@dieknolle3333 I added a draft for the route for the segment bounding box. Find it at /volume/:tracingId/segmentStatistics/boundingBox (same GET parameters as for volume).

I did not build the real implementation in the backend yet, so for now the route will always return this json:
{"topLeft":[5,5,5],"width":10,"height":20,"depth":30}

I hope to get it to return the correct numbers soon.

Note that the bounding box (just as the volume) will be in voxels in the requested mag.

[fm3]

I added the backend implementation now. We may in the future decide to optimize the performance further by doing both statistics in one route or use backend-internal caching, but I didn’t do that yet.

@normanrz could you have a look at the backend changes? Or should we wait for Felix?

[dieknolle3333]

@philippotto so it would be easily possible for me to spend another day testing and reviewing my own code. we planned that I'd finish this PR by yesterday so that I can move on to the next issue, so I fixed bigger issues that occured to me. Having this in mind I am looking forward to your feedback!

[philippotto]

nice stuff :) I already left some feedback. let me know in case you have questions 🤙

[philippotto]

I think, it's fine, but two things:

• please add a usage for replaceAll in frontend/javascripts/libs/browser_feature_check.tsx so that we can warn users about it
• in tsconfig you used es2022. however, you wrote above that es2021 would also suffice. I'd go with 2021 to keep things as backwards-compatible as possible for now (of course, it doesn't make a difference for the compilation output now, but other incompatibilities might sneak in later)

[philippotto]

The CI currently fails. One error seems related to your code. The other might be due to the changed tsconfig. I think, it would be fine to add a @ts-ignore to that.

[philippotto]

Awesome :) I only changed some small details. Also, I made a performance optimization which is actually independent of your changes, but it caught my eye during testing and it was easy to realize.

Will merge as a next step 🚢