Let notifications carry token contexts (OrchestraNotificationEvent::$tokenData) so channels can render custom tokens

Problem

A notification channel that renders tokens (orchestra_easy_email) can only resolve Orchestra's own token types: [orchestra:*] (the instance) and [orchestra-notification:*] (the params). A dispatcher that wants a template to use its own domain tokens has no way to feed the data in without polluting process variables or overloading the notification params.

Proposed resolution

• Add an optional tokenData parameter to OrchestraNotificationEvent: a map of token type to value/entity the dispatcher supplies.
• The token-rendering channel (orchestra_easy_email) merges it into its token replacement data, with Orchestra's own token types keeping precedence on a key collision.
• The params-only mail channel (orchestra_mail) does not render tokens, so it simply ignores tokenData.

This lets any *_notification module surface its own tokens in a template, for example a dispatcher passing ["node" => $node] so a template can use [node:title].

Remaining tasks

• Kernel test coverage that a tokenData-supplied token resolves in the sent email.