infra[QVAC-17058]: add empty BCI whispercpp workflow stubs to enable branch dispatch

[ishanvohra2]

Note: be concise and prefer bullet points.

🎯 What problem does this PR solve?

• New packages/bci-whispercpp addon needs CI workflows, but those workflows are being iterated on a feature branch and cannot be manually dispatched until they are registered on main.
• GitHub Actions only allows workflow_dispatch against a non-default branch when a workflow file with the same name already exists on the default branch — otherwise the workflow is invisible to the API/UI.

📝 How does it solve it?

• Adds 11 no-op stub workflow files under .github/workflows/ mirroring the qvac-lib-infer-whispercpp lineup:
  • benchmark-bci-whispercpp.yml
  • benchmark-performance-bci-whispercpp.yml
  • cpp-test-coverage-bci-whispercpp.yml
  • create-github-release-bci-whispercpp.yml
  • integration-mobile-test-bci-whispercpp.yml
  • integration-test-bci-whispercpp.yml
  • on-merge-bci-whispercpp.yml
  • on-pr-close-bci-whispercpp.yml
  • on-pr-bci-whispercpp.yml
  • prebuilds-bci-whispercpp.yml
  • repository-dispatch-bci-whispercpp.yml
• Each stub uses on: workflow_dispatch: only (no push / pull_request triggers) so it cannot fire on unrelated PRs or merges to main.
• The single job is a no-op echo clarifying that the real implementation lives on the bci-whispercpp feature branch.

🧪 How was it tested?

• YAML is valid and intentionally minimal; once merged, dispatch will be verified from the feature branch via gh workflow run <file>.yml --ref <branch>.

[ogad-tether]

Looks good. These are dispatch-only stubs, so they should register the BCI workflow IDs on main without adding push/PR behavior. I did not find any blocking follow-ups.

[ishanvohra2]

/review

[github-actions]

Tier-based Approval Status

**PR Tier:** TIER1

**Current Status:** ✅ APPROVED

**Requirements:**
- 1 Team Member approval ✅ (1/1)
- 1 Team Lead OR Management approval ✅ (1/1)



---
*This comment is automatically updated when reviews change.*