fix(events): stop a failed dispatch from looking like a delivered one

[hakeemRash]

Releases kernel 1.13.1. Two defects in EventBus, one incident: a listener bound with bindInternal() is unresolvable from outside its module scope, and the bus resolves listeners from outside every module scope. That cost a real tenant membership, and neither half of the bus would say so.

resolveListener() destroyed the cause

The container refused with a ScopeViolationException naming the scope, the class and the fix. It was caught, discarded, and replaced with new, which threw ArgumentCountError — so the log read "Too few arguments to function …::__construct()". Readers went to the listener's constructor, which was correct, instead of to the binding, which was not. The same shape had been misdiagnosed twice before.

new is now attempted only when it can actually succeed (no required constructor parameters) — the case the fallback was always for. Otherwise the container's own exception is rethrown untouched.

dispatch() reported success for an event nobody handled

Isolating a broken subscriber is right; leaving the caller unable to tell isolation from success is not. A transactional outbox marked its row dispatched because dispatch() returned normally — the row was consumed, never retried, and the seat was lost for good, while the table recorded status=1, attempts=1, last_error=NULL.

dispatch() now returns the failures it isolated, keyed by listener class, empty on full success. Additive and backward compatible: every existing $bus->dispatch($e); ignores it and behaves exactly as before. Anything that RECORDS a delivery should check it and re-queue instead of consuming.

Verification

Reproduced the original failure with the broken listener still in place: the outbox row survived as pending instead of being consumed, and the next relay run assigned the seat. A standalone harness covers all four paths — mis-scoped arg-taking listener (real cause surfaced, not ArgumentCountError), no-arg listener still falling back to new, container-resolved happy path, and isolation preserved across a broken + healthy subscriber pair.

Consumed by hkm-plugin-user ^2.2, whose outbox no longer marks a failed dispatch as delivered.