Event routing for pdo event sourcing

[jlabedo]

Description

Routing for projection event handlers has same behavior as standard event handlers, allowing to use object or named routing.

Considering this event class:

#[NamedEvent(self::NAME)]
class AnEvent
{
    public const NAME = 'test.an_event';

    public function __construct(public readonly string $id)
    {
    }
}

One would be required to listen to event name for the projection:

#[Projection(self::NAME, AnAggregate::STREAM_NAME)]
class AProjection
{
    #[EventHandler(AnEvent::NAME)] // <-- event name required here
    public function onEvent(AnEvent $event): void
    {
    }
}

With this PR, it is optional to declare event name in attribute:

#[Projection(self::NAME, AnAggregate::STREAM_NAME)]
class AProjection
{
    #[EventHandler] // <-- event name is not required
    public function onEvent(AnEvent $event): void
    {
    }
}

Type of change

• New feature (non-breaking change which adds functionality)

Pull Request Contribution Terms

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

[unixslayer]

What was the reason for this change? Checking compatibility is more complex than only instanceof considering union types, etc. Wouldn't this bring a BC Break?

[jlabedo]

Checking compatibility is more complex than only instanceof considering union types, etc. Wouldn't this bring a BC Break?

Is it different when the type is a class ? For other types I understand, but for a class I think instanceof is equivalent.

What was the reason for this change?

I already made this type of change in another class some time ago. Here I get an error so I continued the refactor.

[jlabedo]

Ok, the only difference I have in mind is if you use a UnionTypeDescriptor, which is a bit awkward to me:
$interfaceToCall->hasMethodAnnotation(TypeDescriptor::create('AClass|BClass'))

I remove this refactor