fix(react-components): improve loading reveal 3d resource by removing unnecessary caching

[danpriori]

Type of change

Jira ticket 📘

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

It removes the cache system which is no longer triggered when loading the Reveal3DResource component, leaving other apps that use the same component free to forcefully load this cache unnecessarily. And expose the hooks to use the cache system in the app level instead.

This change comes along with the fusion PR: which let the Search UI app use this caching system for scenes and single model which is used by Rule Based Coloring atm.

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.