Add a default Event to dispatch events with just a name

[phil-davis]

Description

In Symfony 5, eventDispatcher->dispatch must be passed an Event as the first parameter, followed by the event name.
In Symfony 4, an event can be dispatched with just a name (as the first parameter) or can have an Event and name (the Symfony 5 call interface)

This PR adjusts the remaining eventDispatcher->dispatch calls so that thet all pass an event as the first parameter.

Related Issue

#39630

How Has This Been Tested?

CI

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Database schema changes (next release will require increase of minor version instead of patch)
• Breaking change (fix or feature that would cause existing functionality to change)
• Technical debt
• Tests only (no source changes)

Checklist:

• Code changes
• Unit tests added
• Acceptance tests added
• Documentation ticket raised:
• Changelog item, see TEMPLATE

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

66.7% Coverage
0.0% Duplication

[DeepDiver1975]

So updating the dispatch to Symfony 5 will break all apps which dispatch events ..... well so be it ....

[phil-davis]

So updating the dispatch to Symfony 5 will break all apps which dispatch events ..... well so be it ....

Yes, the order of parameters to dispatch changes in Symfony5. In Symfony4 they made the code accept the parameters in both the new and the old orders.

If/when we actually go to Symfony5, we first should get the dispatch calls adjusted in all apps, and get those apps released. They will then work with Symfony4 (and 5).

"Some time later" we can bump core to Symfony5.

I am trying to find the obvious things that need adjusting in core now, and they can be in 10.12. That is a small step forward.

There is security support for Symfony4 to Nov 2023, so we have time to gradually sort this out.