feat: expose Overlay3DCollection

[haakonflatval-cognite]

Type of change

Jira ticket 📘

https://cognitedata.atlassian.net/browse/

Description 📝

In order to use Overlay3DCollections as a DomainObject in react-components, it must be exported explicitly, since it is currently being added into the scene and managed that way directly by the Overlay3DTool with no way to interfere.

Point still up for discussion: Should the Overlay3DCollection only be constructible from Overlay3DTool? The constructor is currently a little ugly (needs access to the viewer's camera manager).

The refactoring in this PR involves moving the intersection logic into Overlay3DCollection, making it usable from the outside. (In my opinion, this should have been done earlier anyway).

How has this been tested? 🔍

Test instructions ℹ️

Checklist ☑️

• I am proud of this feature.
• I have performed a self-review of my own code.
• I have added PR type (Feat, Bug, Chore, Test, Docs, Style, Refactor) to the PR title.
• I have manually tested this for different scenarios (different models, formats, devices, browsers).
• I have commented my code in hard-to-understand areas.
• I have made corresponding changes to the public documentation.
• I have added unit and visuals tests to prove that my feature works to the best of my ability.
• I have refactored the code for readability to the best of my ability.
• I have checked that my changes do not introduce regressions in the public documentation.
• I have outlined any known defects / lacking capabilities in the contents of this PR.
• I have listed any remaining work that should follow this PR in the description or jira/miro/etc.
• I have added TSDoc to any public facing changes.
• I have added "developer documentation" in any package README.md that is related / applicable to this PR.
• I have noted down and am currently tracking any technical debt introduced in this PR.
• I have thoroughly thought about the architecture of this implementation.
• I have asked peers to test this feature.

[github-actions]

There were failures in the visual tests workflow.
Image diffs for visual tests can be downloaded as an artifact here.