Plugin settings info handling rework

[vyncent-t]

Describe the bug

Currently there are some information issues between the storage of the plugin settings and the package.json data.

I.e. when the plugin is not running but there has been changes (either description or the version) the information does not update

I am working on a rework of the local storage and redux slice usage to work with this PR headlamp-k8s/plugins#117

and these related issues:

#2578

To Reproduce

Steps to reproduce the bug:

1. Go to settings
2. Open the package.json of a plugin that is installed and change a text string
3. View the field changed and it should update (it does not without it running)

Are you able to fix this issue?

I cam currently working on a fix

Additional Context

[If needed, add any other info or screenshots about the bug here.]
[Is it a regression? What version of Headlamp did not have this bug?]

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten