values-production.yaml image.repository keys missing /examon/ segment, causes ImagePullBackOff

[fbeneventi]

Context

scripts/build-and-push-images.sh pushes all images to
${REGISTRY}/examon/<image> (e.g. with REGISTRY=ghcr.io/examonhpc,
images land at ghcr.io/examonhpc/examon/mosquitto, etc.). This layout
is reflected consistently in every other values file and in the
local-development, staging, and troubleshoot documentation.

deploy/helm/examon/values-production.yaml is the only values file
that omits the /examon/ segment: lines 112, 129, 157, 182 set
repository: ghcr.io/examonhpc/<image>, which does not match any
image actually published by the build script.

Impact

Operators following the production install path
(docs/administrators/deploy/harden-for-production.md Step 2 / Step 6)
hit ImagePullBackOff on every subchart pod that uses these four
keys: KairosDB, Mosquitto, mqtt2kairosdb, examon-server.

Desired behaviour

Add the /examon/ segment to all four image.repository keys in
values-production.yaml:

• ghcr.io/examonhpc/kairosdb -> ghcr.io/examonhpc/examon/kairosdb
• ghcr.io/examonhpc/mosquitto -> ghcr.io/examonhpc/examon/mosquitto
• ghcr.io/examonhpc/mqtt2kairosdb -> ghcr.io/examonhpc/examon/mqtt2kairosdb
• ghcr.io/examonhpc/examon-server -> ghcr.io/examonhpc/examon/examon-server

This aligns the production overlay with the script's push paths and
matches the convention already in values-local.yaml,
values-staging.yaml, and all documentation.

Files to touch

• deploy/helm/examon/values-production.yaml (lines 112, 129, 157, 182)

Doc cleanup when closed

None. The public documentation already describes the post-bugfix
layout consistently; no doc edit accompanies this issue.