Set aksDeployBranch and templates ref to wildfly40 for WF40 deploy

[allanmckenzie]

Why

The first Java 25 / WildFly 40 release run (after PR #31 merged) failed at the Deploy Validation Stack step:

helm install listing-service ... Error: context deadline exceeded

Root cause: the deploy pulled the old wildfly-app chart 0.25.3, which only ships standalone config for WildFly 10 and 26.1.2 (no WF40). The WF40 listing-service image booted against a WildFly 26 standalone.xml, never became ready, and Helm --wait timed out.

The WF40 deploy config (chart 0.25.4-wildfly40 + wildfly.version: 40.0.0.Final, via helmsman_vars/validation25.env) lives on the wildfly40 branches of cpp-azure-devops-templates and cpp-aks-deploy. listing's pipeline was still pointing at main/default.

What

Align listing with the already-working usersgroups and prosecution-casefile pipelines:

• cppAzureDevOpsTemplates repository resource ref: main → wildfly40
• context-validation.yaml parameter aksDeployBranch: 'wildfly40'

CI-config only — no code or Maven changes. Local full reactor build + ITs were already green before merge.

🤖 Generated with Claude Code

[cpp-github-management]