feat(deploy-ocpp-gateway): allow overriding infra-portal host and path prefix

[tobias0106]

What

Two new optional inputs on the deploy-ocpp-gateway composite action, both defaulting to '':

input	default behaviour when empty
infra-portal-hostname	infra-portal.internal.monta.app for dev/staging, infra-portal.monta.app otherwise
infra-portal-path-prefix	/api/public for dev/staging, empty otherwise

Empty = today's stage-derived logic, unchanged.

Why

Today host and path prefix are both derived from stage, and stage cannot be changed — it also builds the namespace segment of the URL (${service-identifier}-${stage} must equal the k8s namespace) and feeds the manifest paths. So a production-stage release is hard-wired to:

https://infra-portal.monta.app/<context>/<ns>/create-gateway-release

which is the legacy releaser. That one only speaks ALB Ingress — getTrafficWeightsFromIngress does a plain Ingresses(ns).Get() with no IsNotFound fallback (api/legacy/internal/ocpp-gateway-rollout/Helper.go:481-489). The gateway on main-production runs ingress.enabled: false behind Envoy Gateway API, so the release aborts.

The v2 releaser handles HTTPRoute weights, but it lives only on the internal portal and registers at /api/public/... (api/core/internal/ocppgatewayreleaser/routes.go:25). Reaching it from a production stage needs both a different host and a different prefix — hence two inputs rather than one.

Compatibility

gh api "search/code?q=org:monta-app+deploy-ocpp-gateway" returns three hits: service-ocpp's deploy-gateway-staging.yml and deploy-gateway-production.yml, plus this action's own README. Neither caller passes the new inputs, so both keep their exact current URLs.

Consumer PR: monta-app/service-ocpp#3077

Follow-ups, deliberately not in this PR

• The README still claims the staging host is infra-portal.staging.monta.app and doesn't document infra-portal-context.
• infra-portal-token is interpolated straight into the curl argv. It is masked in logs but lands in the process argument list. Moving it (and github.sha) into an env: block would be a cheap hardening win.