app-catalog: Added app-catalog to artifact hub

[aadhil2k4]

fixes: #412

This PR adds initial Artifact Hub metadata for the App Catalog Headlamp plugin. This enables discovery of the plugin on Artifact Hub and allows it to be referenced from the Headlamp website.

[aadhil2k4]

@illume Can you please check this PR and let me know if all the details are correct. Please let me know if I have made any mistake or missed something.

[illume]

Thank you for this.

It's a bit more complicated, because we need to change the name of the plugin inside package.json to be in @headlamp-k8s/ namespace. Then we have to make sure we don't break anything with that change. Headlamp itself will need to be updated because it relies on using the current package name for downloading the plugin (there are some app-catalog scripts in the headlamp repo).

(There might be other places that need updating. But those are the only two places I can remember at the moment)

[Copilot]

Pull request overview

This PR adds Artifact Hub metadata for the app-catalog plugin, enabling its discovery on Artifact Hub and integration with the Headlamp website. The metadata file follows the established pattern used by other Headlamp plugins.

Changes:

• Added artifacthub-pkg.yml metadata file for the app-catalog plugin with version 0.8.0

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[illume]

Please see the git commit guidelines and look at other git log messages.

Something like:

app-catalog: Add artifacthub-pkg.yml metadata

[aadhil2k4]

Thank you for this.

It's a bit more complicated, because we need to change the name of the plugin inside package.json to be in @headlamp-k8s/ namespace. Then we have to make sure we don't break anything with that change. Headlamp itself will need to be updated because it relies on using the current package name for downloading the plugin (there are some app-catalog scripts in the headlamp repo).

(There might be other places that need updating. But those are the only two places I can remember at the moment)

@illume For the package namespace changes, should I implement them in this PR or raise a follow up PR as it requires updates in Headlamp repo as well?

[illume]

I think in this PR and a headlamp repo or would be good.

[Copilot]

Pull request overview

Copilot reviewed 2 out of 3 changed files in this pull request and generated 2 comments.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The package-lock.json contains extensive dependency updates (Babel, esbuild, rollup, Storybook, TypeScript ESLint plugins, and many others) that appear unrelated to adding Artifact Hub metadata. These updates seem to have been triggered by running npm install. Consider whether these dependency updates should be:

1. Included in this PR (if intentional and tested)
2. Split into a separate PR focused on dependency updates
3. Reverted if they were unintentional

The package-lock.json changes should ideally be minimal for this PR, only updating the package name from "app-catalog" to "@headlamp-k8s/app-catalog" without upgrading all dependencies, unless the dependency updates are intentional and have been tested.

[aadhil2k4]

@illume I regenerated the package-lock.json after updating the package. Isnt it the correct way?