Smoke-test the bundle the way Dikte starts it

The CPU run passed -ng, which tells whisper.cpp not to look for a
backend at all, so the claim the bundle rests on, that it starts and
transcribes where Vulkan cannot, was never tested. Dikte passes -ng only
when its GPU setting is off; every other run goes through the backend
registry.

Both runs lose the flag, and a third one is added between them: the
loader installed, nothing behind it. That is a real machine, libvulkan
pulled in by something else with no driver to go with it, and it is the
one whose answer nobody knew.

.github/workflows/whisper-vulkan.yml

@@ -110,6 +110,9 @@ jobs:
       - name: CPU fallback smoke test (no Vulkan loader)
         run: OUT_DIR=dist packaging/whisper-vulkan/smoke-runtime.sh cpu
 
+      - name: Vulkan loader present, no device smoke test
+        run: OUT_DIR=dist packaging/whisper-vulkan/smoke-runtime.sh noicd
+
       - name: Vulkan plugin-load smoke test (Mesa llvmpipe)
         run: OUT_DIR=dist packaging/whisper-vulkan/smoke-runtime.sh vulkan