ci: install Bowire cascade-listener workflows (bowire-released + auto-tag)

[thomas-stegemann]

What

Installs the two cascade-listener workflow files from Kuestenlogik/Bowire's .github/sibling-templates/ — verbatim, no per-repo edits:

• .github/workflows/bowire-released.yml — listens for the repository_dispatch: bowire-released event fired by Bowire's release.yml, bumps every Kuestenlogik.Bowire* <PackageVersion> to the new version, opens a PR that the existing dependabot-auto-merge.yml picks up.
• .github/workflows/auto-tag-on-bowire-merge.yml — on merge of those PRs (label bowire-cascade), patch-bumps this repo's own version and pushes a fresh tag, which kicks off this repo's own Release.

Why now

This repo carries the GitHub topic bowire-cascade (the opt-in marker that tells Bowire's release.yml to dispatch to it), but it lacks the listener workflows — so Bowire v2.0.0's cascade silently no-op'd here on 2026-06-21. After this PR merges, the next Bowire release auto-bumps this repo without a manual PR.

Secrets required

Both workflows reference the org-secret BOWIRE_DISPATCH_TOKEN (already in place from the cascade consolidation).

Follow-up

After this merges, the v2.0.0 bump for this repo still needs to happen manually (or trigger a one-off repository_dispatch with event_type: bowire-released, client_payload: {version: 2.0.0}). Future Bowire releases land automatically.

[codecov]

Welcome to Codecov 🎉

Once you merge this PR into your default branch, you're all set! Codecov will compare coverage reports and display results in all future pull requests.

ℹ️ You can also turn on project coverage checks and project coverage reporting on Pull Request comment

Thanks for integrating Codecov - We've got you covered ☂️