feat: support closures in attributes and closure expressions (Enterprise)

[dgafka]

Why is this change proposed?

PHP 8.5 allows closures inside attributes, but using one in any Ecotone attribute crashed container compilation with Serialization of 'Closure' is not allowed (fixes #649). This PR fixes that, and builds on it to let every expression property accept a Closure as a type-safe, refactorable, IDE-friendly alternative to Symfony expression strings (Ecotone Enterprise).

Description of Changes

• Fix (Support of closures in Attributes #649): AttributeDefinition now carries an AttributeDeclaration (declaring class/method/parameter). When an attribute cannot be serialized, the container re-reads it via reflection at runtime — works with both the in-memory and the dumped/cached container.
• Enterprise feature: every expression property accepts string|Closure: #[Payload], #[Header], #[Reference], #[Fetch], #[AddHeader], #[Delayed], #[TimeToLive], #[Deduplicated], #[DbalParameter], #[WithTenantResolver].
• New ClosureExpressionEvaluator executes the closure like a message handler — closure parameters resolve via #[Payload] (with conversion), #[Header], #[Headers], #[Reference], #[ConfigurationVariable], Message type-hints, and first-parameter-defaults-to-payload. DbalParameter closures map parameters by name to the same context string expressions see.
• Without an Enterprise licence, using a closure expression throws LicensingException (covered by tests for each path).

Usage examples

#[CommandHandler('order.place')]
public function placeOrder(
    PlaceOrder $command,
    #[Header('token', expression: static function (#[Header('token')] string $token, #[Reference] TokenService $tokenService): string {
        return $tokenService->normalize($token);
    })] string $token,
): void {}

#[Delayed(expression: static function (#[Payload] NotifyCustomer $command): int {
    return $command->delayInMilliseconds;
})]
#[Asynchronous('async')]
#[CommandHandler('customer.notify', endpointId: 'customerNotifyEndpoint')]
public function notify(NotifyCustomer $command): void {}

#[DbalWrite('INSERT INTO persons (person_id, name) VALUES (:personId, :fullName)')]
#[DbalParameter('fullName', expression: static function (string $firstName, string $lastName): string {
    return $firstName . ' ' . $lastName;
})]
public function insert(int $personId, string $firstName, string $lastName): void;

Use cases

1. Complex header/payload derivation with full IDE support and static analysis instead of expression strings.
2. Dynamic message delay/TTL computed from the command with real type safety.
3. Deduplication keys and tenant resolution derived from message data without learning the expression language.

Flow

sequenceDiagram
    participant Compile as Container Compilation
    participant Dumped as Dumped Container
    participant Evaluator as ClosureExpressionEvaluator
    participant Handler

    Compile->>Compile: attribute contains Closure - cannot serialize
    Compile->>Dumped: store AttributeDeclaration (class/method/parameter)
    Note over Dumped: runtime boot
    Dumped->>Dumped: re-read attribute via reflection - live Closure
    Dumped->>Evaluator: evaluate(Closure, Message)
    Evaluator->>Evaluator: resolve closure parameters (Payload, Header, Reference, ...)
    Evaluator->>Handler: converted argument / enriched header

Loading

Pull Request Contribution Terms

• I have read and agree to the contribution terms outlined in CONTRIBUTING.