feat: detect and alert outdated plugin/provider versions

[MadhavDhatrak]

Added version detection logic that extracts installed versions for providers (Kubernetes CR labels) and plugins (OpenEverest API) and compares them against the latest catalog versions. It displays an "Update available" badge in the catalog table and shows an update warning banner along with the helm upgrade command in the detail drawer if a newer version is available.

Closes #14

I have tested these changes locally by building the Docker image and verifying them on OpenEverest v2. See the screenshots below:

@spron-in You can verify the changes

Also some feature we should consider for Plugin Hub is:

• It can be directly bundled with OpenEverest v2, so when a user installs OpenEverest, they can automatically access Plugin Hub.
• On clicking Update / Uninstall / Install, the actions can be handled via Helm. This could be a really cool feature to add here.
• We can improve the UI a little bit as well (I'm really bad at UI design too 😅). We can create sub-issues describing the changes we want, review them together, and then anyone interested from the community can pick them up.

Let me know your thoughts!

[spron-in]

It can be directly bundled with OpenEverest v2, so when a user installs OpenEverest, they can automatically access Plugin Hub.

this is already done when you install dev.2 release.

As for your PR - do you think we should tackle also non-production versions? Like 1.2.3-rc or 1.2.3-beta? Which are also correct according to semver.

[MadhavDhatrak]

this is already done when you install dev.2 release.

Great, I was on dev.1

As for your PR - do you think we should tackle also non-production versions? Like 1.2.3-rc or 1.2.3-beta? Which are also correct according to semver.

Yes, absolutely! We can handle non-production versions as well. I will update the comparison logic in catalog.ts and push the update to this PR shortly.

[MadhavDhatrak]

I have updated src/catalog.ts to implement SemVer pre-release precedence comparison now it can tackle also non-production versions as well

Tested on a K8s cluster across various pre-release and stable version transitions:

e.g. testing 0.2.0-rc.1 installed against catalog 0.2.0

@spron-in You can verify the changes