… between 2 messages (lyrixx)

This PR was merged into the 5.4 branch.

Discussion
----------

[Mesenger] Add support for reseting container services between 2 messages

| Q             | A
| ------------- | ---
| Branch?       | 5.4
| Bug fix?      | no
| New feature?  | yes
| Deprecations? | no
| Tickets       |
| License       | MIT
| Doc PR        | symfony/symfony-docs#15796

Without this patch, services are not resetted. For example Monolog
Finger Cross handler is never reset nor flushed. So if the first
message trigger and "error" level message, all others message will log
and overflow the buffer.

So, when a transport is **async** (it means it is run in a worker), it's highly preferable to this configuration on

Usage with framework:

```yaml
framework:
    messenger:
        transports:
            async:
                dsn: '%env(MESSENGER_TRANSPORT_DSN)%'
                reset_on_message: true
            failed: 'doctrine://default?queue_name=failed'
            sync: 'sync://'
```

Commits
-------

488bb88 [Mesenger] Add support for resetting container services after each messenger message.