fix: standardize component naming to hyphenated format

[Copilot]

Description

Component names were inconsistent across the codebase: directories and images used backend-py/backend-java (correct), while Helm values, templates, and workflows used backendPy/backendJava/backendGo (incorrect) or backendpy/backendjava (incorrect).

Standardized all references to hyphenated format: backend-py, backend-java, backend-go.

Changes

Helm Charts (charts/app/)

• Renamed template directories: backendPy/ → backend-py/, backendJava/ → backend-java/
• Renamed template files: backendPy-*.yaml → backend-py-*.yaml, backendJava-*.yaml → backend-java-*.yaml
• Updated values.yaml keys: backendPy: → backend-py:, backendJava: → backend-java:, backendGo: → backend-go:
• Updated helper template functions and Values references to use (index .Values "backend-py") syntax
• Updated Kubernetes labels: backendpy → backend-py, backendjava → backend-java

GitHub Workflows (.github/workflows/)

• pentests.yml: Updated matrix names to use hyphenated format
• merge.yml: Updated --set parameters and integration test URLs
• pr-validate.yml: Updated markdown link URLs

Type of change

• Breaking change (fix or feature that would cause existing functionality to not work as expected)

Breaking Changes

⚠️ Route hostnames and resource names will change:

• Before: {release}-backendpy, {release}-backendjava
• After: {release}-backend-py, {release}-backend-java

Existing deployments using Helm values with old naming (backendPy, backendJava, backendGo) must update to new naming (backend-py, backend-java, backend-go).

How Has This Been Tested?

• Helm template syntax validation (helm template with test values)
• Verified route hostnames render with hyphenated format
• Verified Kubernetes labels use hyphenated format
• CodeQL security scan passed
• Code review completed

Checklist

• I have read the CONTRIBUTING doc
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have already been accepted and merged

Further comments

27 files changed, 208 insertions(+), 208 deletions(-)—purely refactoring with no functional additions. All naming now consistent across directories, images, Helm charts, Kubernetes resources, and CI/CD workflows.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>fix: inconsistent component naming</issue_title>
<issue_description>Our components do not follow consistent naming across templates, deployments, folders, ZAP scans and more. Make them consistent without breaking everything!

Good names:

• backend-py
• backend-java

Bad names:

• backendpy
• backendPy
• backendjava
• backendjava</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes fix: inconsistent component naming #420

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

---

Thanks for the PR!

Deployments, as required, will be available below:

• Java
• Py

Please create PRs in draft mode. Mark as ready to enable:

• Analysis Workflow

After merge, new images are deployed in:

• Merge Workflow