[RFC] [DebugBundle] [HttpKernel] Avoid using container as dependency for DumpListener
minor #12584 [RFC] [DebugBundle] [HttpKernel] Avoid using container as dependency for DumpListener (jeromemacias)

This PR was squashed before being merged into the 2.6 branch (closes #12584).

Discussion
----------

[RFC] [DebugBundle] [HttpKernel] Avoid using container as dependency for DumpListener

| Q             | A
| ------------- | ---
| Bug fix?      | kinda
| New feature?  | no
| BC breaks?    | no
| Deprecations? | no
| Tests pass?   | yes
| Fixed tickets | n/a
| License       | MIT
| Doc PR        | n/a

Usage of the `container` service as dependency avoid using the listener outside of a Symfony project.

I don't know if the lazy loading of the dumper service is really required. We should only use the `DebugBundle` in `dev` environment.
If it break performance, maybe we can consider using the `lazy="true"` parameter in services definition.

I currently working on a Silex [`DebugServiceProvider`](https://github.com/jeromemacias/Silex-Debug) which use the `DebugBundle` to avoid duplicating the dump profiler view (like it's done by the `WebProfilerServiceProvider`).
Those modifications are required by the provider to be usable.

Commits
-------

680fe7a [RFC] [DebugBundle] [HttpKernel] Avoid using container as dependency for DumpListener