Clean gh-pages Helm repository

[razinbouzar]

Clean gh-pages branch for Helm chart repository

Summary

This PR cleans the gh-pages branch so it can be used only as the published Helm chart repository for Apache Druid Operator.

The branch currently contains source-tree files that were accidentally merged into gh-pages. This change removes those files and leaves a Helm-compatible empty repository index:

index.yaml

After the publishing workflow runs, the expected branch layout will be:

index.yaml
helm-releases/
  druid-operator-<chart-version>.tgz

Merge Order

Do not merge this PR until #26 has merged.

PR #26 adds the Helm chart publishing workflow and ASF GitHub Pages configuration on master. This cleanup PR only prepares the gh-pages branch to host generated Helm repository content.

Why

gh-pages should not contain the source repository. It should only contain static files served by GitHub Pages. For the Helm chart repository, that means:

• index.yaml
• packaged chart archives under helm-releases/

Keeping gh-pages minimal avoids serving unrelated source files and gives the publishing workflow a clean target branch.

Validation

The resulting branch tree contains only:

index.yaml

The index.yaml file was generated with Helm from an empty repository and is valid as an initial Helm repository index:

apiVersion: v1
entries: {}
generated: "<timestamp>"

Follow-up

After PR #26 and this PR both merge, run the manual Helm Chart workflow from master with publish=true. That workflow will:

1. package the chart
2. copy it to gh-pages/helm-releases/
3. regenerate gh-pages/index.yaml
4. push the published Helm repository content back to gh-pages

Fixes #XXXX.

Description

---

This PR has:

• been tested on a real K8S cluster to ensure creation of a brand new Druid cluster works.
• been tested for backward compatibility on a real K*S cluster by applying the changes introduced here on an existing Druid cluster. If there are any backward incompatible changes then they have been noted in the PR description.
• added comments explaining the "why" and the intent of the code wherever would not be obvious for an unfamiliar reader.
• added documentation for new or modified features or behaviors.

---

Key changed/added files in this PR

• MyFoo
• OurBar
• TheirBaz