feat: inject attributes declared on handler into closure expressions (Enterprise)

[dgafka]

Why is this change proposed?

Closure expressions can resolve #[Header], #[Payload], #[Reference] and friends, but not an Attribute declared on the handler they sit on. A closure parameter type hinted with such an Attribute was treated as the payload, or looked up as a service in the container, and failed with a misleading error.

This left configuration and behaviour unable to sit together: an Attribute can declare policy next to the endpoint, but the expression deciding how to act on that policy could not read it. The same closure had to be duplicated per variation, or the policy hardcoded into the closure.

Description of Changes

• Closure expression parameters type hinted with an Attribute are now resolved against the owning method first, then the owning class.
• Reuses the existing AttributeBuilder / AttributeReference mechanism, so the attribute is resolved lazily through reflection and survives the dumped container (covered cold and warm).
• No new licence gate — VerifyEnterpriseLicenceForClosureExpressions already covers anything reached through a closure expression.
• Adds ConsoleCommandTenantPropagationTest, covering tenant header propagation into #[ConsoleCommand] and onward into a Command Bus sub-flow.

Example

Configuration is declared once as an Attribute, and a single shared closure adapts to it:

final class OrderService
{
    #[DedupPolicy(scope: 'customer')]
    #[Deduplicated(expression: static function (
        DedupPolicy $policy,
        #[Header('customerId')] string $customerId,
        #[Header('orderId')] string $orderId,
    ): string {
        return $policy->scope === 'customer' ? $customerId : $orderId;
    })]
    #[CommandHandler('order.process')]
    public function process(): void
    {
        // deduplicated per customer
    }
}

Changing scope to 'order' switches deduplication to per order, with the closure left untouched.

Pull Request Contribution Terms

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

Drafted with /superpowers:test-driven-development, /superpowers:verification-before-completion, /ecotone-contributor.