…el Logger (cyve)

This PR was squashed before being merged into the 4.4 branch.

Discussion
----------

[HttpKernel] Remove EOL when using error_log() in HttpKernel Logger

| Q             | A
| ------------- | ---
| Branch?       | 4.4
| Bug fix?      | yes
| New feature?  | no
| Deprecations? | maybe
| Tickets       |
| License       | MIT
| Doc PR        |

Hello there !

Since PR symfony/symfony#36855, when using `Symfony\Component\HttpKernel\Log\Logger`  with argument `$output = null`. The logger use the `error_log()` method to log messages. But in the log file, messages are separated by an empty line because the default formatter (`Logger::format()`) adds an extra EOL char at the end of the message.

This fix prevents the logger to add an extra EOL char when it uses `error_log()`.

Possible BC : if someone use the logger with a custom formatter that already add a EOL char at the end of the message, there will be a empty line between messages in the log file. In my opinion, this is minor enough not to worry about it ;-)

Thanks for your review :-)

Commits
-------

69cf83ea1a [HttpKernel] Remove EOL when using error_log() in HttpKernel Logger

… exception (krzyc)

This PR was squashed before being merged into the 4.4 branch.

Discussion
----------

[HttpKernel] Fix empty request stack when terminating with exception

| Q             | A
| ------------- | ---
| Branch?       | 4.4, 5.4, 6.0, 6.1, 6.2
| Bug fix?      | yes
| New feature?  | no
| Deprecations? | no
| Tickets       | Fix #47577
| License       | MIT
| Doc PR        |

After symfony/symfony#47358 the RequestStack is empty when request terminates with exception, which prevents SecurityDataCollector to generate logout URL and generates fatal error.

Commits
-------

e4d6e7b4ba [HttpKernel] Fix empty request stack when terminating with exception