[code-health] Separate state slices on explorer engine and improve code quality

[rubenaprikyan]

This PR includes architectural changes on ui core.
Created new explorer-engine which consists of different engines pipeline, instructions, visualizations, custom-states, groupings, query.
Each engine has data access layer (DAL) and business logic layer(BL), called state and engine respectively.
i.e. pipeline s DAL(state) includes data coming from pipeline, current applied groupings, query , pipeline step, status etc. and corresponding selectors. And BL includes group and search methods to search and group from UI.
The rest of engines has the same structure.
This architectural changes are made to create the ui core maintainable, reusable and keep single responsibility for each BL.
This will help to write robust unit and integration tests, It is easy to create new "BaseExplorer" on top of the explorer-engine.

Remarkable changes

• Integrated redux devtool for zustand store
• Added a way to inject individual visualizations with box and controls
• Changed the public api of BaseExplorer configuration
• Defined default components, configurations for BaseExplorer
  The user may
  • Create its own config
  • Use default hydrations
  • Pass only required configurations

[rubenaprikyan]

Resolves #2146

[KaroMourad]

great work!