Allows job payloads to be dispatched and received as typed DTO objects instead of plain arrays, while maintaining full backward compatibility with existing array-based jobs.

Key Features:

• QueueManager::push() now accepts a DTO object directly, or a plain array paired with an explicit dtoClass option (metadata for uniqueness hashing / debugging)
• New Message::getDto(ExpectedDto::class) hydrates the payload into the class the job asks for — the expected type comes from application code, not from the message body, so a tampered queue message cannot choose which class is instantiated. getArgument() still returns the raw array unchanged. getDtoClass() exposes any dtoClass recorded at dispatch time as metadata only
• Two hydration styles, matching CakePHP 5.4's own DTO conventions (#[RequestToDto], SelectQuery::projectAs()): constructor reflection (with nested DTOs and #[CollectionOf]), and a static createFromArray() factory
• shouldBeUnique dedupe hashing now factors in dtoClass, so two different DTO types with coincidentally identical data are never treated as duplicates of each other
• Fully backward compatible for dispatch — legacy array-only pushes produce byte-identical message bodies. On receive, getDto() throws when the expected class is missing or the payload cannot be hydrated; jobs that still accept legacy arrays can catch that or keep using getArgument()

Usage:

$order = new OrderDto(id: 7, customer: 'Acme Corp', items: [
    new OrderItemDto(sku: 'SKU-1', quantity: 2),
]);

QueueManager::push(ProcessOrderJob::class, $order);

// Or, array payload + optional dtoClass metadata:
QueueManager::push(ProcessOrderJob::class, $data, [
    'dtoClass' => OrderDto::class,
]);

class ProcessOrderJob implements JobInterface
{
    public function execute(Message $message): ?string
    {
        $order = $message->getDto(OrderDto::class);
        return Processor::ACK;
    }
}

Note: requires bumping cakephp/cakephp from ^5.1.0 to ^5.4 (needed for ResultSetFactory::hydrateDto() / DtoMapper), plus php from >=8.1 to >=8.2 to match. Since this raises the floor for every existing installation — not just DTO users — this should ship as 3.0.0 off a new 3.x branch rather than a 2.x minor/patch release, with the version bump called out explicitly in the changelog/release notes.