fix: update WhatsApp bridge dependencies

[ljcarreira-galaico]

Summary

• Updates the WhatsApp bridge Baileys pin to rc13 to clear GHSA-qvv5-jq5g-4cgg.
• Updates Express to 4.22.2.
• Raises protobufjs and ws overrides to patched ranges.

Verification

• cd scripts/whatsapp-bridge && npm audit --omit=dev → found 0 vulnerabilities.
• node --check bridge.js → exit 0.
• npm test --if-present → exit 0.

[alt-glitch]

This was generated by AI during triage.

Duplicate of #43840, which bumps the WhatsApp bridge Baileys pin to v7.0.0-rc13 clearing the same critical GHSA-qvv5-jq5g-4cgg and was opened earlier (closed PRs #45957 and #43934 were already marked duplicates of it). This PR adds Express/protobufjs/ws audit bumps on top, which are worth folding into the canonical #43840 if useful. Maintainer to pick.

[teknium1]

Thanks for the dependency-security update. This is already implemented on current main; closing as superseded by automated hermes-sweeper review.

• scripts/whatsapp-bridge/package-lock.json:757-759 resolves the published @whiskeysockets/baileys 7.0.0-rc13. GHSA-qvv5-jq5g-4cgg is patched from 7.0.0-rc12, so this satisfies the reported critical advisory.
• The same lockfile already resolves the additional audit targets at equal or newer versions: Express 4.22.2 (:1069), protobufjs 7.6.5 (:1654), and ws 8.21.0 (:2156).
• Commit c30c9753b6efc08e154d66b6501a444739df3859 made the registry-based rc13 update and shipped in v2026.7.7.2.
• This also addresses the earlier duplicate discussion pointing to fix(whatsapp): bump Baileys pin to v7.0.0-rc13 to fix LID-addressed group sends #43840 while preserving the newer registry-install approach on main.