Added persistence from within a cluster

[mpRegalado]

This PR is a direct enhancement of #1135
With these changes, the current extension state is saved to the Splunk Database instead of to a local file. This means that multiple installations of the plugin will read data from a single origin, achieving a consistent state.

Closes #1142

To test

These same tests should work identically when navigating to Agent Extensions instead of Overview Welcome.
Tests should work either in a single installation or across multiple search heads.
Fresh start

• Given a new API has been set up
• And There is no extensions data in session storage
• When The user navigates to Overview/Welcome for the first time
• Then Extensions load as described in SplunkAppForWazuh/default/config.conf
• And Extensions data is added to session storage

Enabling an extension

• Given the browser is in Overview/Welcome
• When the user enables an extension
• Then the extension appears in the menu

Reloading form same session

• Given there is Extensions data in session storage
• And the extensions have been modified previously
• When the browser navigates to Overview/Welcome
• Then extensions load to match previous changes

Reloading from a new session

• Given there is no extensions data in session storage
• And this API's extensions have been modified previously
• When the user navigates to Overview/Welcome
• Then extensions load to match previous changes
• And an entry in extensions data is added with identical information to the one added in a fresh start

Removing an API

• Given there is an API set up
• And there is extension data in session storage
• When the user removes an API
• Then extension data for this API is removed from session storage

[CPAlejandro]

CR: LGTM!
Testing: LGTM!

[asteriscos]

CR: ✔️
Test: ✔️

[gabiwassan]

LGTM!