Seems prettier was getting stuck somehow on the headlamp-plugins
folder... could not find why with debugging enabled. So instead
we just list the folders it should format instead.

So current npm LTS is happy.

Both peerDependencies and peerDependenciesMeta are unused AFAIK.
The typescript version is old, and es-lint package doesn't exist.

So that current npm installs quicker with it.

When using create --link, the package wasn't linked when using the
new npm.

So plugins can `npm run tsc` and see issues.

This is because various libraries in node_modules can be broken,
and we only really care to see if the plugin code type checks.

So the instructions are a bit better on what to do.

Merge pull request #422 from kinvolk/dependabot/npm_and_yarn/plugins/examples/pod-counter/path-parse-1.0.7

build(deps): bump path-parse from 1.0.6 to 1.0.7 in /plugins/examples/pod-counter

Merge pull request #421 from kinvolk/dependabot/npm_and_yarn/plugins/examples/pod-counter/y18n-4.0.3

build(deps): bump y18n from 4.0.0 to 4.0.3 in /plugins/examples/pod-counter

Merge pull request #420 from kinvolk/dependabot/npm_and_yarn/plugins/examples/pod-counter/ssri-6.0.2

build(deps): bump ssri from 6.0.1 to 6.0.2 in /plugins/examples/pod-counter

Merge pull request #419 from kinvolk/dependabot/npm_and_yarn/plugins/examples/pod-counter/browserslist-4.19.1

build(deps): bump browserslist from 4.14.2 to 4.19.1 in /plugins/examples/pod-counter

Dockerfile: Fix alpine version typo, and separate front and back building

So that if a src/ change is made it doesn't do an npm install again.

So that if a backend part is changed, then the frontend image is
not rebuilt and vice versa.

Fix plugin reinitialization

Upgrade Nodejs 16 versions, and Alpine linux 3.15.0

Bumps [path-parse](https://github.com/jbgutierrez/path-parse) from 1.0.6 to 1.0.7.
- [Release notes](https://github.com/jbgutierrez/path-parse/releases)
- [Commits](https://github.com/jbgutierrez/path-parse/commits/v1.0.7

)

---
updated-dependencies:
- dependency-name: path-parse
  dependency-type: indirect
...
Signed-off-by: dependabot[bot] <support@github.com>

Bumps [y18n](https://github.com/yargs/y18n) from 4.0.0 to 4.0.3.
- [Release notes](https://github.com/yargs/y18n/releases)
- [Changelog](https://github.com/yargs/y18n/blob/y18n-v4.0.3/CHANGELOG.md)
- [Commits](https://github.com/yargs/y18n/compare/v4.0.0...y18n-v4.0.3

)

---
updated-dependencies:
- dependency-name: y18n
  dependency-type: indirect
...
Signed-off-by: dependabot[bot] <support@github.com>

Bumps [ssri](https://github.com/npm/ssri) from 6.0.1 to 6.0.2.
- [Release notes](https://github.com/npm/ssri/releases)
- [Changelog](https://github.com/npm/ssri/blob/v6.0.2/CHANGELOG.md)
- [Commits](https://github.com/npm/ssri/compare/v6.0.1...v6.0.2

)

---
updated-dependencies:
- dependency-name: ssri
  dependency-type: indirect
...
Signed-off-by: dependabot[bot] <support@github.com>

Bumps [browserslist](https://github.com/browserslist/browserslist) from 4.14.2 to 4.19.1.
- [Release notes](https://github.com/browserslist/browserslist/releases)
- [Changelog](https://github.com/browserslist/browserslist/blob/main/CHANGELOG.md)
- [Commits](https://github.com/browserslist/browserslist/compare/4.14.2...4.19.1

)

---
updated-dependencies:
- dependency-name: browserslist
  dependency-type: indirect
...
Signed-off-by: dependabot[bot] <support@github.com>

headlamp-plugin: Bump version to 0.4.0

Mainly for the new nodejs 16 LTS, but also pg 14, and linux LTS.

Because Nodejs 16 is now LTS node, and it has various improvements
including better support for javascript modules.

frontend: Make workload details go back to the correct list view

Fix UI warnings

frontend: Fix warning color's contrast on dark theme

frontend: Check for a pod's conditions before using them

Those were disableBackdropClick and disableEscapeKeyDown.

This prevents a warning in the version of material-ui currently used.

Better info for workloads

For some reason the plugins were being reinitialized when the theme
was changed which also ended up in a reload of all components. This
shouldn't be needed, so this patch removes that logic.

We had an issue related to re-initializing the plugins when they've
already be initialized, this ended up re-registering the same plugin
functionality and thus would result in getting duplicated sections
and potentially other issues.

While re-initialization of plugins should be avoided altogether, the
logic for initializing them should make sure the plugins and their
states are reset before initialization which is what this patch does.