Publish a pre-release for scheduled operator builds

The createRelease job only ran on workflow_dispatch, so the daily
scheduled builds — which produce the operator versions that actually
get deployed — pushed a v<version> tag but published no GitHub Release.

The uid2-deployment pre-deploy release gate (UID2-6767, #4068) hard-blocks
any deploy/rollback of a non-SNAPSHOT version that has no published Release,
so those scheduled-build versions would block on deploy.

Run createRelease on scheduled builds too, reusing the existing pre-release
logic. Scheduled runs are always release_type 'patch' (never Snapshot),
and the public child build keeps force_release:'no', so no double-release.

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

Author: BehnamMozafari

.github/workflows/publish-all-operators.yaml

@@ -151,7 +151,13 @@ jobs:
   createRelease:
     name: Create Release
     runs-on: ubuntu-latest
-    if: github.event_name == 'workflow_dispatch'
+    # Also publish on scheduled builds, not just manual dispatch: the deployed
+    # operator versions come from the daily scheduled run, so gating this on
+    # workflow_dispatch left those versions tagged but with no GitHub Release.
+    # The uid2-deployment pre-deploy release gate (UID2-6767) then hard-blocks
+    # any deploy/rollback of such a version. Scheduled runs are always
+    # release_type 'patch' (never Snapshot), so no Snapshot-release edge case.
+    if: github.event_name == 'workflow_dispatch' || github.event_name == 'schedule'
     needs: [start, buildPublic, buildGCP, buildAzure, buildAWS, buildAMI]
     steps:
       - name: Checkout repo