working on feature versioning mechanism

[aalves08]

Fixes #170

Implement feature versioning mechanism that's bound to Elemental backend version, which is captured from the elemental-operator deployment label app.kubernetes.io/version.

This impact areas such as:
-BuildMedia (support for RAW disk image build) which can be found in Dashboard view and machine registration detail view.

• machine registration cloud config, which can be found in machine registration create view.

To test:

• Install elemental-operator-crds manually, via kubectl (so it installs the dev version with the label):

helm upgrade --create-namespace -n cattle-elemental-system --install elemental-operator-crds oci://registry.opensuse.org/isv/rancher/elemental/dev/charts/rancher/elemental-operator-crds-chart

• Install elemental-operator manually, via kubectl:

helm upgrade --create-namespace -n cattle-elemental-system --install elemental-operator oci://registry.opensuse.org/isv/rancher/elemental/dev/charts/rancher/elemental-operator-chart

• Run this branch and check the areas above mentioned:

-`BuildMedia` (support for RAW disk image build) which can be found in `Dashboard` view and `machine registration` detail view.
- `machine registration` cloud config, which can be found in `machine registration` create view.

• Edit pkg/elemental/utils/feature-versioning.ts lines 18-37, change version number there displayed and check impact on each of the areas mentioned (no support for RAW disk image build and smaller cloud config for machine registration)

Screenshots of areas of impact

[mantis-toboggan-md]

I was able to test the PR using the instructions provided and overall it looks good and works. I had a minor suggestion about the implementation of the version gating mechanism but it's totally non-critical.

[mantis-toboggan-md]

LGTM