fix: gate record-connector-registry on docker job success

The job condition checked binaries and windows but not docker. When
goreleaser-docker failed, the manifest and S3 upload still ran with
incomplete release artifacts (missing container images).

Add docker result check: must be success or skipped (skipped when
docker=false && lambda=false).

Author: gontzess

.github/workflows/release.yaml

@@ -909,8 +909,9 @@ jobs:
 
   record-connector-registry:
     # require binaries to succeed; windows and docker may be skipped (msi=false, docker=false && lambda=false)
+    # docker must succeed if it ran — a failed docker build means incomplete release artifacts
     # see: https://docs.github.com/en/actions/using-jobs/using-conditions-to-control-job-execution
-    if: ${{ !cancelled() && needs.goreleaser-binaries.result == 'success' && (needs.goreleaser-windows.result == 'success' || needs.goreleaser-windows.result == 'skipped') }}
+    if: ${{ !cancelled() && needs.goreleaser-binaries.result == 'success' && (needs.goreleaser-windows.result == 'success' || needs.goreleaser-windows.result == 'skipped') && (needs.goreleaser-docker.result == 'success' || needs.goreleaser-docker.result == 'skipped') }}
     needs: [determine-workflows-ref, goreleaser-binaries, goreleaser-windows, goreleaser-docker]
     permissions:
       id-token: write