fix: make bd gateway compatible across old/new beads versions

[web3dev1337]

Summary

• add runtime compatibility detection in BDGateway for bd --no-daemon
• use --no-daemon when supported (older beads), omit it when unsupported (newer beads)
• add retry fallback: if a command returns unknown flag: --no-daemon, rerun without the flag and cache support as disabled
• expand unit coverage for probe caching, unsupported-flag mode, and runtime fallback retry

Why

Newer upstream beads releases reject --no-daemon, while older environments may still expect it. This makes GUI bead operations compatible across old/new CLI versions.

Validation

• baseline before changes: npm test (pass)
• after changes: npm test (pass)
• frontend/e2e re-check: npm run test:e2e (pass)
• npm run build is not defined in this repo (no build step)