Add commands for inspecting configured listeners

[HypeMC]

Related to doctrine/DoctrineBundle#2032

Similar to Symfony's debug:event-dispatcher command, this PR adds two new commands to inspect configured Doctrine event/entity listeners:

• orm:debug:event-manager — lists event listeners registered in the Doctrine EventManager for a given entity manager (optionally filter by event).
• orm:debug:entity-listeners — lists entity listeners configured for a given entity class (optionally filter by event).

[github-actions]

There hasn't been any activity on this pull request in the past 90 days, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 7 days.
If you want to continue working on it, please leave a comment.

[HypeMC]

Still waiting for review 😄

[derrabus]

Those commands looks reasonable and helpful to me. WDYT @greg0ire?

[derrabus]

Suggested change

	private function getMockManagerRegistry(): MockObject
	private function getMockManagerRegistry(): ManagerRegistry

Let's pick the more obvious type here and in the other tests.

[derrabus]

Please flag this class as @internal. I don't want it to be used downstream.

[greg0ire]

Those commands looks reasonable and helpful to me. WDYT @greg0ire?

I think so too.

[greg0ire]

Can we get a few screenshots? Also, should the new commands be documented here?

[HypeMC]

@derrabus @greg0ire Hi, thank you for the review. All comments have been addressed in 47496ed.

Here are some screenshots as requested:

[greg0ire]

Now that I'm seeing the result I'm thinking that maybe event should just be a column of one big table, rather than having many tables of length 1.

But I don't know how realistic your examples are.

[HypeMC]

Now that I'm seeing the result I'm thinking that maybe event should just be a column of one big table, rather than having many tables of length 1.

But I don't know how realistic your examples are.

@greg0ire The listeners for each event are sorted by priority, which to me is one of the main benefits of these commands, being able to clearly see the execution order. Putting everything into one table would make that harder to read.

[greg0ire]

How about you add a table separator between each event, if this is a concern? You can even use a rowspan

+------------------------+-------+---------------------------------------------------------------------+
| Event                  | Order | Listener                                                            |
+------------------------+-------+---------------------------------------------------------------------+
| loadClassMetadataEvent | #1    | Doctrine\ORM\Tools\Pagination\LimitSubqueryWalker::addFilterToQuery |
|                        | #2    | App\EventListener\AuditListener::loadClassMetadata                  |
+------------------------+-------+---------------------------------------------------------------------+
| onFlush                | #1    | Doctrine\ORM\Tools\Pagination\LimitSubqueryWalker::addFilterToQuery |
+------------------------+-------+---------------------------------------------------------------------+
| onSchemaCreateTable    | #1    | Doctrine\ORM\Tools\Pagination\LimitSubqueryWalker::addFilterToQuery |
+------------------------+-------+---------------------------------------------------------------------+

[HypeMC]

@greg0ire Done, I think it looks better now:

[greg0ire]

Gorgeous!

[greg0ire]

Thanks @HypeMC !