feat(react-components): Add filter command and make mocks for the settings commands.

[nilscognite]

Type of change

Jira ticket 📘

No Jira ticket

Description 📝

• Make mocks to simulate the different possibilities:

• Add filter with optional color

Details:

• Added virtual method getChildren. Used where it was possible.
• New base class: BaseFilterCommand for handling filter
• Some refactoring of the commands to make method names and some other names more homogeneous. And reuse getChildren() in the base classes. This eliminated some code around.
• Made mock classes for various scenarios.
• Made PointCloudFilterCommand for controlling the point filter.

Details on the React side

• New component FilterButton and FilterItem.
• The Filterbutton can be as a separate button or part of the settings. Same with the CommandButton.
• The rest of the changes is made to get the code more homogeneous.
• Fixed so the dropdown menus is closed when click outside. It was buggy before.
• I have not done this for the settings dropdown. This is because we get the click outside event when the options or filtering is open and clicked. I have to investigate this further in another PR.

How has this been tested? 🔍

Go to Story book/Architecture
Click in the "Bug" icon for testing all settings
Click in "Filter" icons for test the stand alone filter.

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]

LGTM