Update internal repo to support non-root user scenario

Related to: https://github.com/Azure/data-api-builder/issues/3514

Background

Public PR Azure/data-api-builder#3520 restructured the sample Dockerfile into a multi-target build with two runtime variants:

• runtime (default / last stage) — runs as root, backwards-compatible with today's published image.
• runtime-nonroot (opt-in via --target runtime-nonroot) — runs as USER $APP_UID (UID 1654), satisfies scanners (e.g. Checkmarx One) that require a non-root Config.User.

The public Dockerfile is only a customer sample. The image we actually publish is built from the internal repo, which has its own Dockerfile + release pipeline YAML — both need updating to publish the second tag.

Tasks

• Update the internal Dockerfile to match #3520 (multi-stage runtime-base → runtime / runtime-nonroot, USER $APP_UID, non-recursive chown $APP_UID:$APP_UID /App/logs).
• Update the pipeline to build + push both images: root (:<version>, :latest) and non-root (--target runtime-nonroot → :<version>-nonroot, :latest-nonroot).
• Run signing, SBOM/manifest, and registry push for both tags.
• Point the container scan gate at the -nonroot image.
• Update release notes / image README with the two variants and non-root consumer caveats.

Commencez par comparer le Dockerfile interne et le YAML du pipeline de release avec les changements du PR public #3520. Le travail est terminé lorsque les tags root et non-root sont tous deux construits, signés et inclus dans la SBOM/manifest et les pushes vers le registry, que le scan gate cible l’image non-root et que les release notes ou l’image README décrivent les deux variantes et leurs limites.