WIP - frontend: PluginSettings: Refactor local storage and plugin data

[vyncent-t]

This is the rework for the local storage plugin settings usage

• This PR shrinks the saved JSON data from the plugins information and saves only the name and isEnabled in the local storage, this is what allows the plugin settings to be saved when closing and starting the app again

• This PR also handles backwards compatibility that allows previous settings saved to be used in this new format

• This PR also no longer takes old information stored in the JSON of the local storage and instead takes it from the backend when the main Plugin component is called

[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