Add a method to clear all messages from a channel

まず AdapterInterface と既存の push/status エントリポイントを読み、次に Redis、AMQP、インメモリのアダプターを調査します。purge と clear の命名、およびチャネルシグネチャに関する問題を解決してください。opt-in インターフェースと提案されたアダプター実装によって、プライマリインターフェースを変更せずにチャネルを空にできれば完了です。

Proposed new feature or change

There's no programmatic way to empty a queue. It comes up in three places:

1. Maintenance - a queue:purge command or an admin button to drop a queue that got flooded with poison pills or jobs that are no longer wanted.
2. Deployments - clearing a queue during a release when the payload structure changed and old queued jobs would crash on the new code.
3. Testing - resetting state between runs. Shelling out to redis-cli or rabbitmqctl makes the test suite fragile and awkward to run in containerized CI.

I wouldn't put this on AdapterInterface - that would break every existing implementation and it overlaps with the "not the job of the primary interface" point from #271. A separate opt-in interface fits better:

interface PurgeableInterface
{
    public function purge(): void;
}

Adapters implement it when the backend can do it cheaply (Redis drops the channel keys, AMQP calls queue_purge, the in-memory adapter resets its array). Callers check for it:

if ($adapter instanceof PurgeableInterface) {
    $adapter->purge();
}

Open questions:

1. Name: purge() (broker vocabulary) or clear()?
2. Signature: purge(): void on the adapter's current channel (consistent with push/status, which don't take a channel) or purge(string $channel)?

Worth pursuing? Happy to send a PR if you're good with it (core + redis/amqp).