Queues: add API to immediately dead-letter a specific message

Cloudflare Queues push consumers currently expose ack/retry controls, and configured DLQs receive messages only after max_retries is exhausted.

**Feature request:** add a push-consumer API to immediately dead-letter a specific message, for example:

```ts
message.deadLetter({ reason?: string })
```

**Use case:** a consumer can classify some failures as terminal/non-retryable, such as programmer bugs, malformed-but-preservable payloads, or invariant failures. Today the choices are either:

- ack the message and lose the payload, or
- retry/fail the message until max_retries so Cloudflare moves it to the configured DLQ, even though retries are known to be useless, or
- manually publish a custom failure envelope to a separate queue and then ack the original.

An immediate dead-letter primitive would let consumers preserve terminal failures in the configured DLQ without wasting retry attempts and without building a parallel application-level DLQ mechanism.

**Relevant docs:**
- https://developers.cloudflare.com/queues/configuration/dead-letter-queues/
- https://developers.cloudflare.com/queues/configuration/batching-retries/

Commencez par la documentation de Cloudflare Queues sur le dead-letter et le batching/retries, liée dans l’issue, puis examinez l’API existante d’ack et de retry du push-consumer. Définissez le comportement d’une opération de dead-letter spécifique à un message et d’une raison facultative ; le travail est considéré comme terminé lorsque les échecs terminaux atteignent immédiatement la DLQ configurée sans consommer de tentatives de retry.

Rédigé par le modèle d'indexation à partir du texte de l'issue.