fix: #3587709 Services should not keep the container

Alexander Varwijkrequested to merge
issue/graphql-3587709:3587709-services-not-have-container into 5.x

Services should not keep the container. This refactors two scenarios where that occurs.

The Executor uses the Factory directly to pass on the dependencies, rather than delegating this, which allows removing the create method.

For the PasswordReset data producer a test is written to document the current behaviour. Then the controller instantiation from the container is moved to a HTTP sub-request that calls the controller directly. This allows injecting the HTTP kernel rather than the entire container.

Closes #3587709

Merge request reports