feat(react-components): Generalize settings popup

[nilscognite]

Type of change

Jira ticket 📘

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

Description 📝

Generalize settings with the following settings as use case:

• High/low Quality
• Point size
• Point color
• Point shape

Code change in the non-React side

• Some fixes of comments and small code changes around
• BaseCommand added isToggle method if this command is a real toggle. This is implemented on the sub classes where it was relevant.
• Used RenderTargetCommand as base instead of BaseCmd since it made the code easier
• BaseSliderCommand for making sliders for numbers
• KeyboardSpeedCommand made easier and more according to other similar commands
• SetPointColorTypeCommand, SetPointShapeCommand, SetPointSizeCommand, and SetQualityCommand new command holding a specific toggle.
• SettingsCommand for holding all the settings command above

Code change in the React side:

• Let the tooltip can be undefined. Then it is disabled. Used for the the settings, since it jives too much information.
• CommandButtons: check for SettingsCommand since this is special handled.
• OptionButton : New property, usedInSettings, which is true if it is a part of the settings. This will bale the appearance somewhat different. Removing the icon code, since it wasn't used. Refactored.
• SettingsButton is new. Make the settings buttons and all the setting.
• useClickOutside is new. Handle when click outside of the OptionButton. Code copied from fusion.

How has this been tested? 🔍

For the moment I do not know how to test it in storybook, since must settings is for the point cloud.
I have tested it by mocking it myself, but I cannot commit this change in.

The only test you can do is:

1. Open storybook/architecture.
2. Click in the settings icon in the toolbar
3. Change the quility toggle

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.

[pramodcog]

Works really great.
Added few comments

[pramodcog]

LGTM!
One minor comment to address before you merge.