feat(fm): deploy Helm charts on partners, both ways

FM only onboarded container images at a partner, and TF-SDK's Kubernetes
adapter only runs Helm, so no CAMARA app could reach a partner zone at all.

Outbound, a Helm unit goes to the partner as a GSMA HELM artefact with the
chart in artefactRepoLocation. GSMA still wants every component to name its
images as uploaded files, and a CAMARA Helm app names only the chart, so FM
reads them from the chart's values.yaml (image.repository and tag, with
Chart.yaml's appVersion as the default tag; subcharts aside) and uploads one
DOCKER file per image. A chart that isn't an http(s) .tgz, or declares no
image that way, is refused before anything reaches the partner. Container
units keep their file ids.

Inbound, FM accepts a HELM artefact from a public repository and turns it into
one helm deployment unit for SRM, with the components' resources added up.

pyyaml moves from the dev extras to the runtime dependencies.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>