Stub the full Queue Pause/Resume surface on QueueFactory

[imorland]

The problem

Flarum's QueueFactory is bound as the 'queue' / Factory service and handed to Illuminate's Worker in the role normally filled by the full QueueManager. But the Factory contract only guarantees connection() — every other method the worker or queue commands call on the manager is something QueueFactory has to provide itself.

Illuminate's Queue Pause/Resume feature keeps growing that manager-level surface, and QueueFactory has been catching up only after each one breaks production:

• isPaused() had to be added when the worker started calling it.
• getPausedQueues() had to be added in [2.x] Add getPausedQueues() to QueueFactory for illuminate/queue v13.11+ compatibility #4673 when illuminate/queue v13.11's worker began calling it, crashing the queue with «Call to undefined method» and silently breaking all queued notifications and mail.

Both methods live on QueueManager, not on the queue connection, so there's no general fallback protecting us — the next pause method wired into the worker will break things the same way.

What this does

Stubs the whole Queue Pause/Resume family up front, so a future Illuminate release calling any of them can't crash the worker:

• Adds no-op pause(), pauseFor(), resume() and withoutInterruptionPolling().
• Fixes getPausedQueues() to take ($connection, $queues), matching the QueueManager contract and the worker's actual call — it previously only worked because PHP silently drops extra positional arguments.
• Adds a : bool return type to the existing isPaused() for consistency.

Signatures mirror Illuminate\Queue\QueueManager. Queue pausing itself remains unsupported for now — these are deliberate no-ops — but it is planned for a future Flarum version, noted with a TODO.

Notes

A generic __call() forwarding to the connection (like QueueManager has) was considered and rejected: it would not have prevented either past crash, because the pause methods don't exist on the queue connection either. Explicitly stubbing the bounded manager-level family is the targeted fix.