ci: repair the consumer-verify wiring GitHub refused to load

The daily schedule's minute and hour fields had been shifted out of the cron
expression and into bundle_image, in BOTH consumer-verify.yml and release.yml:

    - cron: " * * *"          # three fields; GitHub requires five
      bundle_image: 53 9        # the missing two, as an image name

GitHub rejected the workflow file outright -- every push to dev reported a
red 'This run likely failed because of a workflow file issue' with no job and
no log -- and the daily rot check that file exists to run had never fired once.

bundle_image is now empty, which is the truthful value: this repo publishes one
kind of artifact, a signed busbar-store-*.tar.gz per target, and no container
bundle appears in any of its workflows. Empty makes the shared workflow declare
the runnable-bundle boot check NOT-APPLICABLE rather than silently skip it. The
comment claiming this repo ships a runnable bundle came from headroom-hook and
was never true here.

Pre-existing on dev (#4), independent of the durable-store work landing beside
it; fixed here because it made every push to dev read as red.

Author: MattJackson

.github/workflows/consumer-verify.yml

@@ -22,7 +22,7 @@ on:
   release:
     types: [published]
   schedule:
-    - cron: " * * *"
+    - cron: "53 9 * * *"
   workflow_dispatch:
     inputs:
       version:
@@ -47,9 +47,10 @@ jobs:
       plugin_name: busbar-store-sqlite-plugin
       plugin_alias: sqlite
       plugin_kind: store
-      # This repo publishes a runnable bundle, so the check does not stop at 'the tarball exists':
-      # the image is pulled fresh and the container must BOOT and answer /healthz. That is the
-      # assertion that was missing when the published bundle shipped a config busbar had retired.
-      bundle_image: 53 9
+      # EMPTY, and correct: this repo publishes exactly one kind of artifact, a signed
+      # busbar-store-*.tar.gz per target (see release.yml's `plugin-dist/*.tar.gz` upload) -- no
+      # container bundle anywhere in this repo's workflows. `bundle_image: ""` makes the shared
+      # workflow declare the runnable-bundle boot check NOT-APPLICABLE rather than silently skip it.
+      bundle_image: ""
       bundle_env: ""
     secrets: inherit

.github/workflows/release.yml

@@ -271,10 +271,11 @@ jobs:
       plugin_name: busbar-store-sqlite-plugin
       plugin_alias: sqlite
       plugin_kind: store
-      # This repo publishes a runnable bundle, so the check does not stop at 'the tarball exists':
-      # the image is pulled fresh and the container must BOOT and answer /healthz. That is the
-      # assertion that was missing when the published bundle shipped a config busbar had retired.
-      bundle_image: 53 9
+      # EMPTY, and correct: this repo publishes exactly one kind of artifact, a signed
+      # busbar-store-*.tar.gz per target (see release.yml's `plugin-dist/*.tar.gz` upload) -- no
+      # container bundle anywhere in this repo's workflows. `bundle_image: ""` makes the shared
+      # workflow declare the runnable-bundle boot check NOT-APPLICABLE rather than silently skip it.
+      bundle_image: ""
       bundle_env: ""
     permissions:
       contents: read