frontend: PluginSettings: Refactor local storage and plugin data

[vyncent-t]

Fixes Issue #2595

Description

• This PR shrinks the saved JSON data from the plugins information and saves only the name and isEnabled status in local storage. This ensures plugin settings persist when closing and reopening the app.
• This PR introduces the usePlugins hook into lib/k8s/api/v2
• It also handles backward compatibility, allowing previously saved settings to be used in this new format.
• Additionally, it no longer takes old information from the JSON in local storage. Instead, it retrieves the necessary plugin data from the backend when the main Plugin component is called.

Changes

1. Introduces usePlugins hook: Hook used to fetch the plugins from the backend and return the plugins with their settings
2. Reduced Storage Data: Only stores essential plugin info (name and isEnabled) in local storage.
3. Backward Compatibility: Converts old-format data into the new structure on first run.
4. Data Source Shift: Eliminates use of outdated local storage JSON data, and instead fetches plugin details from the backend when the Plugin component mounts.

How to Test

1. Setup:
   • Pull this branch and run the application.
2. Verify Plugin Settings:
   • Open headlamp in app mode
   • Navigate to the settings page then to plugins settings tab
   • Check local storage item headlampPluginSettings
3. Check Backward Compatibility:
   • Start with an older version of the app or start from main.
   • Navigate to the settings page then to plugins settings tab
   • Check local storage item headlampPluginSettings
   • Switch to this branch and run the app.
   • Confirm that previously stored plugin settings are recognized and converted correctly.
4. Backend Data:
   • Verify that after loading, the plugin details (other than name and isEnabled) are fetched from the backend and displayed correctly in the UI.
   • Switch plugins off and on and observe the changes in local storage and in app

Notes

• If you have preexisting local storage data, this PR will convert it automatically. You can reset the local storage if you return to main and go to the same plugin settings paage.
• Double-check the logs to ensure no errors appear during the migration from old data to new data.

[vyncent-t]

Last push adds backwards comp so that all settings wont be set to off or on

[vyncent-t]

I have tried to keep the changes as small as possible to accomplish everything it needs to, I am not using the map object to save information anymore, although to hit these targets I still had to use most of what I had reworked previously

@joaquimrocha @sniok

for this PR the targets it needs to hit were:

• not have the plugins version/data coming from a client-side stored version of it

The plugin data comes from the backend, reused the same method of reaching it from the previous rework

• avoid having to store all that data when what we are interested in is checking whether the plugins are enabled on the user's side

The data is now trimmed down to just being the name and isEnabled, it is now being used the same way as the original settings where this local saved item is how new app start ups save plugin settings

• need to be backwards compatible with the previous settings method

The local storage handling logic checks for the old format and changes it to the new format

[sniok]

Some things to do to avoid duplicating of logic:

• refactor fetching logic into a single place that both PluginSettings and fetchAndExecutePlugins use
• use react-query for fetching to have caching and avoid refetching the same stuff

[vyncent-t]

pushing rebase of current main

[vyncent-t]

note: that last disabled e2e needs to be redone in a later PR as it is out dated with the changes made to two different branches, this branch and the plugins name change branch, this is in my stack for playwright changes I will be working on later

[sniok]

Plugins setting stopped working, check the pod-counter plugin settings

[illume]

@vyncent-t It seems there’s conflicts now. Can you please fix them?

Also, can you please check if the PR description is up to date? I see a lot of changes since the last PR description edit, so I guess if needs updating.