Fix backlinks

frontend: Make class names in k8s.resourceClasses consistent

Use vs-dark theme for every Editor instance we use

Shortcuts

As the monaco-editor doesn't allow having a different themes for
different editor instances because of a global style issue, we should
set a unified theme for every editor instance that we use.

It's very convenient to press a shortcut combination to turn the
mentioned filter start typing for filtering the connected contents.

The cluster chooser was being shown using Ctrl+L which was apparently
fine on Mac OS but on Linux it is also the shortcut for selecting the
URL entry on many browsers. So we replace that shortcut with
Ctrl+Shift+L instead.

This class is extending an existing one, so it needs to override the
class name getter.

The class names have not been set in a consistent way: some are using
a capital first letter, and as a result the names in
k8s.resourceClasses were not the expected ones. We should make the
class names consistent but that has implications in the routes and
the sidebar, so for now we just capitalize the first letter when
adding the classes to k8s.resourceClasses. This is a temporary
measure until we have made de class names consistent.

Misc fixes

Workload related classes (cronJob, DaemonSet, Deployment, Job, and
StatefulSet) should have their list route pointing to the workload
overview since they have no individual views yet.

Instead of having /workload for the list of workloads, we should use
the plural form in order to be consistent with the rest of the routes.

Since the list route name for this component's list view has an
irregular plural, it can not be computed the same way and this
resulted in a broke back button link when in the ingress details view.

This patch fixes that by simply overriding the listRoute property of
the Ingress class.

More plugin actions

These packages required an update related to security. This is the
result of running npm audit fix.

Add plugins NPM pkg

Now that we support external plugins, the infrastructure to compile
those plugins was still not easy to configure. In order to make that
easier and also to provide other useful modules (like types, libs,
etc.) related to the plugins, this patch creates a new NPM package that
developers can use for building the Headlamp plugins externally.

Improve plugins development

The plugins dir option was used in camelCase whereas the other options
were using hyphens, so this patch removes the use of camelCase.

We should have app bar actions for plugins to customize the top bar if
needed. So this patch adds a registerAppBarAction for that purpose.

We removed the possibility of local plugins (modules that use the plugin
library but are built together with the frontend) since we now support
external plugins. However, local plugins may be needed when building
Headlamp with extra functionality, and also for making it easy to
develop plugins before "moving" them outside the Headlamp's tree.

So this patch fetches any external plugins, loads any local ones, and
only then it initializes the full plugins list.

This is a simple change to use the mentioned function definition instead
of redefining the type (in order to DRY).

The header actions are assigned using a name but the key used for the
name had not been updated in the UI reducer. As a result, the header
actions were always assigned to "undefined" and that meant not only that
we would lose the name, but also that only one action would be set up.
This patch corrects the key used for assigning the name.

The plugins folder was being looked for in the backend folder by
default, but that folder will not exist unless using Headlamp from
source. So this patch simply changes the path where Headlamp looks for
the plugins folder to be the current working folder.

frontend: Reset docs when the editor contents change

Fix chooser when more than 3 clusters are available

frontend: Notify the user when the cluster version changes

The docs' view is supposed to react to the contents of the editor. So
when the editor has a certain object kind and api version, the docs
should show the documentation for that object.
However, if there was an error shown (because e.g. the docs were not
found, or the contents were empty) then even if the contents were
corrected by the user, the error would remain.

To fix the mentioned issue, this patch resets the docs' error info
whenever the contents are changed.

When there were more than 2 clusters to be chosen, they were not
fitting correctly in the chooser dialog horizontally and thus would look
very unbalanced visually. This patch fixes that by allowing the grid to
arrange the items automatically.

The chooser dialog has the project logo on top but due to its styling
rules it was not showing the full width of the it depending on the
aspect ration of the logo used (i.e. the width would be cut out).

This patch increases the logo height and fixes the mentioned bug by
setting the width to 100%.

The cluster may be upgraded or downgraded while the user is using it,
but that change is silent because we only fetch the version once.

These changes make the version be fetched every minute, and if it
changes then a snackbar notification is shown informing the user about
that.

Fix the createRouteUrl method

We loop over the routes and render them accordingly. If a route requires
authentication and we don't have the required token we should be
redirected to the choser page but this was failing because while looping
and generating the route url if we pass an empty param with the cluster
url the generatePath(which is a helper from react-router-dom) will fail
because we are passing an empty param to it, In our usecase the empty
param actually means that its a request for the '/' choser page and not
the '/' cluster page. Thus this patch handles this usecase and returns
the choser route url in case of empty param.

 Fix desktop and web app build config

We don't want to build the web app with a relative path which we are
currently doing by specifying the homepage property in package.json
for frontend dir. Instead we only need the relative path build for the
desktop app thus while building the desktop app we specify manually the
host path with the PUBLIC_URL env var.