Add local platform mesh kind setup

[cnvergence]

#49
This PR adds Make target to deploy local platform mesh with deployed example-httpbin-operator via the ocm.

Summary by CodeRabbit

• New Features

  • One-command local platform mesh installation workflow.
  • Automated setup of development hosts entries.
  • Enhanced example operator defaults with enablement and image configuration.
  • Extensive task automation for build, lint, test, package, deploy, and prerelease workflows.
  • Platform mesh configuration manifest enabling integrated components (gateway, auth, infra, portal, virtual workspaces, etc.).

• Chores

  • Expanded ignore rules to cover Helm-related artifacts.

[coderabbitai]

Walkthrough

Adds .helm-charts to .gitignore, updates the Makefile with a TASK variable plus local-platform-mesh and setup-hosts targets, enables the example-httpbin operator in chart values, and introduces a new OCM Taskfile and OCM configuration manifests for prerelease and platform-mesh orchestration.

Changes

Cohort / File(s)	Summary of Changes
Git ignore update ./.gitignore	Added .helm-charts to ignored paths.
Makefile enhancements ./Makefile	Added TASK ?= task; added .PHONY targets local-platform-mesh and setup-hosts; implements cloning Helm charts, preparing OCM config, running TASK workflows, and guarded /etc/hosts append logic.
Chart value change charts/example-httpbin-operator/values.yaml	Added enabled: true and image.name: ghcr.io/platform-mesh/example-httpbin-operator.
OCM Taskfile (new) hack/ocm/Taskfile.yaml	New comprehensive Taskfile defining environment vars and many tasks for setup, build, lint, packaging, OCI registry/transfer, prerelease builds, deployments, TLS handling, and E2E commands.
OCM prerelease component constructor (new) hack/ocm/component-constructor-prerelease.yaml	New prerelease component constructor YAML listing many components, versions, providers, and resources (helm charts and OCI images) and a prerelease aggregation entry.
PlatformMesh manifest (new) hack/ocm/platform-mesh.yaml	New PlatformMesh custom resource manifest with spec, exposure, ocm repo/component refs, and extensive per-component values and TLS/host configurations.

Estimated code review effort

🎯 4 (Complex) | ⏱️ ~45 minutes

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Free

📥 Commits

Reviewing files that changed from the base of the PR and between 66f84a6 and 68f3d39.

📒 Files selected for processing (5)

• Makefile (2 hunks)
• charts/example-httpbin-operator/values.yaml (2 hunks)
• hack/ocm/Taskfile.yaml (1 hunks)
• hack/ocm/component-constructor-prerelease.yaml (1 hunks)
• hack/ocm/platform-mesh.yaml (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• Makefile

---

Note

🎁 Summarized by CodeRabbit Free

Your organization is on the Free plan. CodeRabbit will generate a high-level summary and a walkthrough for each pull request. For a comprehensive line-by-line review, please upgrade your subscription to CodeRabbit Pro by visiting https://app.coderabbit.ai/login.

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[mirzakopic]

@cnvergence Can you please add a bit of context hos this is meant to be used in the larger scope of local setup?

The CodeRabbit does ok to summarize, but i think more is needed there in how this is going to be used in larger picture.

Thanks!

[cnvergence]

@mirzakopic, so I thought we wanted to have this target to deploy platform-mesh in a kind cluster and deploy ocm package with the example-httpbin-operator.
This is the initial automation of the process. We can also document it or document each step independently.

[mirzakopic]

Yep that's correct, would have been just nicer to document that in the PR here :)

[mirzakopic]

lgtm