Update symfony/event-dispatcher requirement from ~4.4 to ~5.3 in /build/integration

[dependabot-preview]

Updates the requirements on symfony/event-dispatcher to permit the latest version.

Release notes

Sourced from symfony/event-dispatcher's releases.

v5.3.0

Changelog (symfony/event-dispatcher@v5.3.0-RC1...v5.3.0)

• no significant changes

Changelog

Sourced from symfony/event-dispatcher's changelog.

CHANGELOG

5.3

• Add #[AsEventListener] attribute for declaring listeners on PHP 8

5.1.0

• The LegacyEventDispatcherProxy class has been deprecated.
• Added an optional dispatcher attribute to the listener and subscriber tags in RegisterListenerPass.

5.0.0

• The signature of the EventDispatcherInterface::dispatch() method has been changed to dispatch($event, string $eventName = null): object.
• The Event class has been removed in favor of Symfony\Contracts\EventDispatcher\Event.
• The TraceableEventDispatcherInterface has been removed.
• The WrappedListener class is now final.

4.4.0

• AddEventAliasesPass has been added, allowing applications and bundles to extend the event alias mapping used by RegisterListenersPass.
• Made the event attribute of the kernel.event_listener tag optional for FQCN events.

4.3.0

• The signature of the EventDispatcherInterface::dispatch() method should be updated to dispatch($event, string $eventName = null), not doing so is deprecated
• deprecated the Event class, use Symfony\Contracts\EventDispatcher\Event instead

4.1.0

• added support for invokable event listeners tagged with kernel.event_listener by default
• The TraceableEventDispatcher::getOrphanedEvents() method has been added.
• The TraceableEventDispatcherInterface has been deprecated.

4.0.0

• removed the ContainerAwareEventDispatcher class
• added the reset() method to the TraceableEventDispatcherInterface

3.4.0

... (truncated)

Commits

• 67a5f35 Merge branch '5.2' into 5.3
• 2ffa4bf Merge branch '4.4' into 5.2
• 047773e Fix CS in README files
• ff708cb Add #[As-prefix] to service attributes
• 36b7381 Deprecate configuring tag names and service ids in compiler passes
• bcbfcf5 feature #40234 [Console] Add ConsoleCommand attribute for declaring command...
• 7855ba3 Merge branch '5.2' into 5.x
• d08d6ec [EventDispatcher] fix registering subscribers twice on edge-case
• a7c8f37 [EventDispatcher] add missing "dispatcher" property on #[EventListener]
• d80457b [Console] Add ConsoleCommand attribute for declaring commands on PHP 8
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in the .github/dependabot.yml file in this repo:

• Update frequency
• Automerge options (never/patch/minor, and dev/runtime dependencies)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)

[juliusknorr]

Seems to be fine for CI I guess as there are no classes shared between the integration tests and our 3rdparty ones but maybe @danxuliu can check if there is anything i'm missing as you've pinned that through ec63327

[danxuliu]

symfony/event-dispatcher 5.2.1 is being used now by Nextcloud, so it should be fine to use 5.X in the integration tests too.

However... the problem back in the day was that SymfonyAdapter::dispatch declaration was not compatible with EventDispatcherInterface::dispatch from Symfony 5.X. But it looks like it is still incompatible. Yet the remote API tests, which were the ones failing back in the day, worked fine 🤷

Maybe the problem is still there but it is just not triggered due to being a deprecated class and fortunately not used? 🤔

Maybe @ChristophWurst knows what is going on :-)

[juliusknorr]

But 3rdparty is still at 4 that is why i was wondering https://github.com/nextcloud/3rdparty/blob/master/composer.json#L49

[ChristophWurst]

Since the test dependencies should not have any influence on production code I'm fine bumping this if tests pass 🤷

[juliusknorr]

The import of base.php in the remote tests is still there, that could have caused the 3rdparty dependency loading so no idea why it would now work all of a sudden, but lets get it in then and move on I'd say.