Consolidate all Helm charts into taskmedia/helm #1

Destination

taskmedia/helm is the single live home for all task.media Helm charts: a working release pipeline (chart-releaser-action, ported from helm-template) publishes charts to gh-pages; main is the default branch; the four legacy chart repos (helm_ipsec-vpn-server, helm_paperlessngx-backup, paperlessngx-ftp-bridge, helm_vpn-ios-profile) and helm-template carry a "moved" notice with a deep link and are archived; and every chart's cross-repo references point at taskmedia/helm. Chart functional behavior/versioning is untouched.

Notes

• Domain: Helm chart release engineering / GitHub repo consolidation for the taskmedia org.
• This map carries execution — tickets here do the work (build the pipeline, write the README, commit notices, archive repos), not just decide it. The destination is the finished repo, not a handoff spec.
• Scope line: fix cross-references to old repos (sources:, links, badges, docs) as part of this effort; do not change chart functional behavior or versioning schemes (e.g. ipsec-vpn-server's appVersion: "latest") — that's separate follow-up work.
• Sequencing: prove the release pipeline end-to-end before flipping the default branch or archiving anything.
• Archiving: the agent performs the actual gh repo archive once the user confirms per repo; before archiving, commit a "moved to taskmedia/helm" notice with a deep link (e.g. https://github.com/taskmedia/helm/tree/main/charts/<name>) to each legacy repo's README first.
• Shell note: GH_HOST defaults to an enterprise instance in this environment — prefix GH_HOST=github.com on every gh command targeting taskmedia/* repos.
• Reference: helm-template's release.yaml uses fty4/helm_chart-releaser-action@v1.8.1-rc1 (a patched fork of chart-releaser-action) — port that pattern rather than reinventing it.

Decisions so far

• Research: pre-flight facts for adopting chart-releaser-action — bump every chart's version before the first chart-releaser run (no reconciliation with legacy gh-pages entries); no Actions permission changes needed; keep using the fty4 fork (upstream fix still unmerged).

Not yet specified

• Whether a CONTRIBUTING.md / chart-authoring guide is needed to replace what helm-template used to document, now that it's being archived.
• Whether dependabot / chart-testing config needs tuning once the full 4-chart set + release pipeline is live.

Out of scope

• Functional/behavioral changes to individual charts (e.g. resolving ipsec-vpn-server's appVersion: "latest" limitation) — separate follow-up work.