[Docs]: Clarify provider-pause behavior for auto-queued work

[zhyongrui]

Summary
Clarify how auto-queued work behaves when a provider pause is active.

Problem to solve
The current operator documentation in docs/openclawcode/operator-setup.md does not explicitly say that auto-queued work can wait behind an active provider pause even when queue intake succeeded.

Proposed solution
Update docs/openclawcode/operator-setup.md with a short note that explains the observable behavior during an active provider pause, including that queue intake can succeed before execution resumes.

• keep the change docs-only
• keep the note specific to operator behavior during active provider pauses

Acceptance criteria

• docs/openclawcode/operator-setup.md explains that auto-queued work can wait behind a provider pause
• the doc also points operators to the queue/status surfaces where the pause is visible
• no runtime code changes are required

Severity
Low.