App framework: build lazy service listeners from app container, not server container

How to use GitHub

• Please use the 👍 reaction to show that you are affected by the same issue.
• Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
• Subscribe to receive notifications on status change and new comments.

Steps to reproduce

1. Register an app listener in the bootstrap logic of your app
2. Use a custom parameter, service or alias in for the constructor injection of the listener

Expected behavior

DI resolves the arguments, the listener is built and executed.

Actual behavior

💥 https://help.nextcloud.com/t/app-development-getting-exception-on-event/119418

The problem is that https://github.com/nextcloud/server/blob/master/lib/private/EventDispatcher/ServiceEventListener.php asks the server container for the service, not the respective app container.

Server configuration

Nextcloud version: Any that supports the lazy event listeners

Start with lib/private/EventDispatcher/ServiceEventListener.php and trace how a listener registered during app bootstrap is constructed. Reproduce the issue with a custom parameter, service, or alias in the listener constructor. Done means dependency injection resolves those arguments and the listener is built and executed using the app container.