Migrate compatible Bitnami-backed DB charts to containerforge with source-based tags

[Copilot]

This PR updates chart image sources to oci.trueforge.org/containerforge only where a matching containerforge source app exists and is compatible.

Changes Made

• Migrated and pinned source-based versions for compatible charts:

  • charts/incubator/valkey
    • image: oci.trueforge.org/containerforge/valkey
    • tag: 7.2.11 (from containerforge app source)
  • charts/stable/mariadb
    • image: oci.trueforge.org/containerforge/mariadb
    • tag: 11.4.8-r0 (from containerforge app source)

• Applied compatibility updates for mariadb to match containerforge image behavior:

  • switched env vars from MARIADB_* to MYSQL_*
  • changed probes to TCP-based checks
  • changed data mount path to /config

• Reverted unsupported migrations (no matching containerforge app source found) back to Bitnami Secure images:

  • charts/stable/redis
  • charts/stable/memcached
  • charts/stable/mongodb
  • charts/stable/wordpress

• Updated chart metadata:

  • bumped chart versions for all affected charts
  • updated source URLs for migrated charts to point to containerforge app sources
  • removed duplicate source entries introduced during follow-up edits

Validation

• Ran targeted pre-commit on all changed chart files.
• Ran automated review/security checks (code_review, codeql_checker) for the final state.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[Crow-Control]

@copilot you made mistakes by prefixing things with bitnamisecure/

Also be sure not to use digests

[Copilot]

@copilot you made mistakes by prefixing things with bitnamisecure/

Also be sure not to use digests

Addressed in 8d1c3a9. I updated all six migrated charts to use oci.trueforge.org/containerforge/<image> (removed the bitnamisecure/ prefix) and changed their tags from latest@sha256:... to latest.

[Crow-Control]

@copilot figure out the latest dag for the containerforge containers based on their source: GitHub.com/trueforge-org/containerforge

Also take that into account to figure out if they are compatible or that changes would be needed to the charts.

[github-actions]

📝 Linting results:

✔️ Linting [charts/incubator/valkey]: Passed - Took 1 seconds
✔️ Linting [charts/stable/mariadb]: Passed - Took 1 seconds
✔️ Linting [charts/stable/memcached]: Passed - Took 1 seconds
✔️ Linting [charts/stable/mongodb]: Passed - Took 1 seconds
✔️ Linting [charts/stable/redis]: Passed - Took 1 seconds
✔️ Linting [charts/stable/wordpress]: Passed - Took 1 seconds
Total Charts Linted: 6
Total Charts Passed: 6
Total Charts Failed: 0

✅ Linting: Passed - Took 2 seconds

[Copilot]

@copilot figure out the latest dag for the containerforge containers based on their source: GitHub.com/trueforge-org/containerforge

Also take that into account to figure out if they are compatible ...

Done in a936c8c and 083e071. I checked trueforge-org/containerforge app sources and used source-defined versions where applicable: valkey -> 7.2.11, mariadb -> 11.4.8-r0. I also adjusted mariadb chart compatibility (MYSQL_* env vars, TCP probes, /config data mount). For redis, memcached, mongodb, and wordpress, matching source app directories are not present in containerforge, so I reverted those repositories back to docker.io/bitnamisecure/* to avoid incompatible migrations. No UI changes in this PR.