Show clicked Bounding Box in BB-Tab

[MichaelBuessemeyer]

URL of deployed dev instance (used for testing):

• https://allowhavingselectedboundingbox.webknossos.xyz

Steps to test:

• Create an annotation of your favourite dataset.
• Use the bbox tool to create a lot of bounding boxes.
• Whenever a new bounding box is created, the bounding box tab should scroll to the bottom and highlight this bounding box.
• Create a lot of bounding boxes to get into a scrolling state in the bbox tab
• When a bounding box is clicked while the bbox tool is active, the bbox should also be highlighted.
• Same goes for resizing

TODOs:

• Scroll selected bbox into view. Maybe Scroll the table to the specified row ant-design/ant-design#6570 helps -> 👎

Open Questions

• Should the context menu support to highlight a bounding box? -> Not necessary now.

Issues:

• fixes #7606

---

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

• Updated changelog

[daniel-wer]

Nicely done, works very well 👍

One more thing that came to my mind, because the view is not the fastest having 20+ bounding boxes (also hasn't been before!): Now that an antd table is used one could try to set the virtual prop and check whether that improves performance. There's no need to do that in this PR, but if you'd like you can try.

[MichaelBuessemeyer]

Sorry @daniel-wer, but I did some code adjustments that need your review:

• I moved the +-button into the footer of the table.
• No longer rendering an empty table in view mode; Instead, nothing is rendered.
• The id prop was removed from the bounding box inputs as a ref to the table supports scrolling the table to a specific element. I did not find this earlier in the docs (only found it while testing virtualizing the table). => The new highlighting does not have a scrolling animation anymore. Afaik this also goes for the other tabs, so I thought this would be fine.

I also tested making the table virtualized but stopped doing so, as it sadly requires setting a specified scroll width and height. In order to get the correct values of width and height I would have needed something like hardcoded calculation of the tab's current width and height. This is due to the tab being resizable. As I wanted to avoid this rather ugly code, I undid my changes and kept the table in a not virtualized state.

So this remains a future TODO.

Could you please recheck the newest version of this PR @daniel-wer

[MichaelBuessemeyer]

And @daniel-wer what do you think about this:

Should the context menu support to highlight a bounding box?

[daniel-wer]

LGTM 👍

Thank you for testing the virtualization! I second your opinion that it's best to look at that as a followup.

Should the context menu support to highlight a bounding box?

I don't think that is necessary as simply clicking on the bounding box will highlight it in the list.