feat(ci): notify QQ of Release, Deployment, and Discussion changes

[openai0229]

Related issue

Closes #2003

Summary

Extend the existing QQ group notification workflow to cover Release lifecycle,
Deployment creation and status updates, and Discussion lifecycle events. The
formatter sends only bounded event metadata and intentionally excludes Release
and Discussion bodies, Discussion comments, Deployment payloads, and URL query
strings that may contain credentials.

Affected surfaces

• Frontend / Web
• Backend / API / Storage
• Database plugin / Driver
• JCEF / Desktop packaging
• CI / Build / Release
• Documentation only

Verification

• Commands and results:
  • python3 script/github/test_notify_qq.py - 17 tests passed.
  • python3 script/github/qq_relay/test_relay_server.py - 13 tests passed.
  • actionlint .github/workflows/ci.yml .github/workflows/qq-group-notifications.yml - passed with no findings.
  • python3 -m py_compile script/github/notify_qq.py script/github/test_notify_qq.py - passed.
  • git diff --check - passed.
• Manual verification: N/A before merge. A representative live repository event
  must be triggered after the trusted notifier lands on the default branch.
• UI evidence: N/A

Risk and compatibility

• Public API or stored data: N/A; no product API or stored data changes.
• Database or driver compatibility: N/A; no database or driver changes.
• Network, privacy, or security: Uses the existing authenticated fixed-group
  relay. New formatters allowlist metadata, omit bodies and Deployment payloads,
  and strip query strings and fragments from Deployment links.
• Community / Local / Pro boundary: Repository automation only; no edition
  runtime behavior changes.
• Backward compatibility: Existing Issue, pull-request, and manual-test message
  paths are unchanged and remain covered by regression tests.

Reviewer map

• Start here: .github/workflows/qq-group-notifications.yml, then
  script/github/notify_qq.py::build_notification.
• Failure condition: A subscribed event does not start the workflow, includes a
  disallowed payload field, or cannot be formatted and accepted by the relay.
• Rollback or disable path: Revert this PR to remove only the new event coverage,
  or disable QQ group notifications to stop all sends immediately.

Contributor declaration

• I linked the Issue that defines this change.
• I tested the affected behavior and reported the actual results above.
• I did not include credentials, private data, or generated build output.
• I disclosed substantial AI assistance below, or this PR contains no substantial AI-generated code.

AI assistance: Codex assisted with implementation, tests, documentation, and
verification; the resulting changes were reviewed against the Issue scope.