chore(release): retarget image and chart publish/pull to the llm-d org

[shimib]

What does this PR do?

Retargets image and Helm-chart publishing and pulling from ghcr.io/llm-d-incubation to ghcr.io/llm-d, following the repo's transfer into the llm-d org. GitHub redirects the git repo on transfer, but GHCR packages do not follow a repo transfer, so every publish/pull path had to move explicitly.

Changes

Publish (release):

• .github/workflows/ci-release.yaml — build/push the release image and trivy-scan it under ghcr.io/llm-d.
• .github/workflows/ci-build-images.yaml — reusable build workflow registry/image.
• scripts/publish-helm-chart.sh — push the chart to oci://ghcr.io/llm-d/charts.

Pull (consumers):

• charts/async-processor/values.yaml — default image repository → ghcr.io/llm-d/llm-d-async (this is the one end users hit on helm install), plus the chart unit-test expectations.
• deploy/install.sh, the e2e default image (test/e2e/e2e_suite_test.go), and docs/guides/e2e-deploy*.

Local/dev: Makefile IMAGE_TAG_BASE.

Out of scope (intentional)

• Go module paths (github.com/llm-d-incubation/llm-d-async/... in go.mods and imports) are left unchanged. They are self-consistent and resolve via GitHub's repo redirect, so builds and go get keep working; renaming the module path is a separate breaking change for downstream consumers (e.g. the batch-gateway operator) and warrants its own PR.

⚠️ Ops prerequisite (not code)

Merging this is necessary but not sufficient — a release will only publish once an llm-d org admin ensures the release workflow's GHCR_TOKEN has write:packages on the llm-d org and the llm-d-async image + charts/async-processor packages can be created there. Existing ghcr.io/llm-d-incubation/* packages keep working via their old path until deleted, so pinned consumers aren't broken immediately.

How was this tested?

• helm template → default image renders ghcr.io/llm-d/llm-d-async:0.7.0
• helm lint clean; helm unittest 49/49 pass
• go vet -tags e2e ./test/e2e/ ok

Release note

Image and Helm chart are now published to and pulled from ghcr.io/llm-d (was ghcr.io/llm-d-incubation).

[j-mok-dev]

@jtechapps @shimib The release workflow (https://github.com/llm-d/llm-d-async/actions/runs/29516135464) is failing on docker-build-and-push after the github.token migration, so ghcr.io/llm-d/llm-d-async:v0.7.4 isn't published yet.
We're trying to consume v0.7.4 downstream (llm-d/llm-d-batch-gateway#590). any ETA on the fix?

[jtechapps]

@j-mok-dev We are working to resolve this ASAP looks like we missed creating package. #327