docs(ci): clarify inactive deployment notification limit

[openai0229]

Related issue

Closes #2003

Summary

Correct the QQ notification operations guide after live Deployment validation.
GitHub Actions does not start a deployment_status workflow for the inactive
state, so the guide now documents that platform exception instead of claiming
that every status update creates a QQ message.

Affected surfaces

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

Verification

• Commands and results:
  • git diff --check - passed.
• Manual verification: Deployment 5584461344 emitted successful deployment
  and deployment_status workflow runs for creation and success; setting it to
  inactive created status 15880351577 but did not start a workflow.
• UI evidence: N/A

Risk and compatibility

• Public API or stored data: N/A; documentation only.
• Database or driver compatibility: N/A; documentation only.
• Network, privacy, or security: N/A; no runtime configuration changed.
• Community / Local / Pro boundary: Community repository operations guide only.
• Backward compatibility: N/A; no behavior changed.

Reviewer map

• Start here: .github/QQ_GROUP_NOTIFICATIONS.md notification coverage section.
• Failure condition: The guide implies inactive can trigger an Actions workflow.
• Rollback or disable path: Revert this documentation commit.

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 live verification and documentation wording.