feat(DMVP-10317): add analytics component charts

[aramkarapetian]

Summary

• add thin Metabase and PostgREST charts backed by DasMeta base 0.3.31
• add a Redash topology chart using five aliased base dependencies and native service commands
• vendor dependency locks for reproducible chart rendering
• add chart READMEs, minimal secret-reference examples, and analytics chart catalog entries

Validation

• helm lint charts/metabase
• helm lint charts/postgrest
• helm lint charts/redash
• helm template for all three charts with their minimal example values

Follow-up

After merge and chart release, terraform-any-analytics will consume the published component-chart versions instead of direct Kubernetes resources.

[what-the-diff]

🌟 PR Summary: Charting The Course to Brilliance 🌟

You folks are awesome for churning out such impeccable work! Let's dive in and see how this update makes us even better! 🚀

• 📊 New Metabase Chart: We've successfully created a brand new Metabase chart! This gives us the essential outline and maps out our core steps, guiding us efficiently towards our goal. Let's give a round of applause to the fantastic tool, charts/metabase/Chart.yaml! 👏

• 🏷️ Values Add Up for Metabase: To help our Metabase perform at its best, we've got precise values set in charts/metabase/values.yaml. These define specifics such as image use, service details, and more. A magical recipe for the best performance! 🎩🐇

• 🕸️ Trusty Base Chart Archive for Metabase: We also tightened our grip with a firm anchor— charts/metabase/charts/base-0.3.31.tgz and made sure our Metabase is stable and ready for action! 🦾

• 🎯 PostgREST Get Its Chart Too: In the spirit of making things better, we created charts/postgrest/Chart.yaml! Similar to Metabase, it uses metadata and dependencies to ensure smoother sailing! 🛠️

• 💼 Values in Place for PostgREST: We've added specific values in charts/postgREST/values.yaml, allowing us to configure specifics such as images, services, and container settings. The finest tailored suit for our dear friend PostgREST! 👔

• 🧱 Steady Base Chart Archive for PostgREST: Following the example of Metabase, we've integrated charts/postgREST/charts/base-0.3.31.tgz. No storm can shake PostgREST off its course now! 🏂

• 🔴 Redash Joins The Chart Club: We're extremely proud to welcome Redash into the chart club! With charts/redash/Chart.yaml, we've mapped out the dependencies for various components and streamlined the whole process! 🕸️

• 🔢 Configured Values for Redash: The values for Redash are locked in charts/redash/values.yaml. We're packing the power to configure everything from servers to workers and their images! 📸

• 🎈 A Secure Base Chart Archive for Redash: Last but definitely not least, we've added our trusty anchor, charts/redash/charts/base-0.3.31.tgz, to make sure Redash is as stable as can be. No hurdles can ever stop us! 💪

The sails are set and the anchors are dropped! It's time for another awesome journey in the sea of coding. Let's keep moving forward and spreading awesomeness everywhere we go! 🚀🌈💡🎉

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 7378756140

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Configure distinct commands for Redash processes

In a default installation, the scheduler and all three worker blocks omit the base chart's command/args, so the Redash image inherits its default server command. Consequently these four Deployments start additional web servers rather than a scheduler or queue workers, leaving scheduled, ad-hoc, and background jobs unprocessed. Set the scheduler/worker commands and each worker's intended queue configuration explicitly.

Useful? React with 👍 / 👎.

[chatgpt-codex-connector]

Preserve release scoping in Redash resource names

When two releases are installed in the same namespace—for example, separate tenant instances or a blue/green rollout—these fixed fullnameOverride values make both releases render the same Deployment and Service names. The second installation therefore collides with resources owned by the first unless callers discover and override all five names; leave these overrides empty or incorporate the Helm release name.

Useful? React with 👍 / 👎.

[chatgpt-codex-connector]

Propagate application versions into the base subcharts

The workloads are rendered in the dependency context, but none of the new wrapper value blocks supplies the base chart's appVersion; its label helper therefore renders app.kubernetes.io/version: 0.3.31 on Metabase, PostgREST, and every Redash Deployment instead of the version of the image being run. This produces incorrect version metadata for selectors, inventory, and monitoring, so set appVersion under each base alias to the corresponding application image version.

Useful? React with 👍 / 👎.

[aramkarapetian]

Addressed the automated review findings in facffd0:

• Redash scheduler and workers use native commands with the official queue and worker-count defaults.
• Component names use release-scoped nameOverride values, avoiding same-namespace release collisions.
• Metabase, PostgREST, and Redash subcharts now propagate their application versions into labels.
• The Redash example uses a YAML anchor for the shared runtime-Secret reference.

Validated with helm lint and helm template for all three charts and their minimal examples.