introduce 'config' Pinia store with other Vuex modules - drop the usage of 'config' Vuex module

[orlinmalkja]

This MR addresses the following:

• create a 'config' Pinia store
• change other components to now use the 'config' Pinia store, instead of 'config' Vuex module
• remove unused code mainly in 'contents' Vuex module
• at the end of this MR: we will have a mixture of ['contents', 'annotations'] Vuex modules and 'config' pinia store

[paulpestov]

I think we should refine this a bit more. The types for different connector options should be more specific. A connector is in fact a real existing component that sits inside of a view (tab). For the sake of modularity we should push towards well-defined APIs (props/events) for each component. This means that we should define specifc types and interfaces for those views. For example a MetadataView component should be configured by a MetadataViewConfigOptions interface.

[orlinmalkja]

I have worked in my previous two commits to address the refinement of Config interface.

[paulpestov]

As discussed, please remove all non TextAPI Types and Interfaces for now and focus just on refactoring to Pinia store. We will deal with the correct typing of configs and their dependencies later.

[orlinmalkja]

@paulpestov yes, I just did it in my last commit:
Additionally in my last commit I did the following:

• removed the Config Vuex Module folder
• used Config Pinia Store in some other components
• used only 'TextAPI' types in 'Config' Pinia store
• removed unused code