Include traces in deprecation logs

[oprypkhantc]

Deprecation logs currently look like this:

pipeline.WARNING: mb_strlen(): Passing null to parameter #1 ($string) of type string is deprecated in /app/modules/Auth/Services/RedisSessionsService.php on line 122
pipeline.WARNING: mb_substr(): Passing null to parameter #1 ($string) of type string is deprecated in /app/vendor/laravel/framework/src/Illuminate/Support/Str.php on line 944  
pipeline.WARNING: mb_substr(): Passing null to parameter #1 ($string) of type string is deprecated in /app/vendor/laravel/framework/src/Illuminate/Support/Str.php on line 944  
pipeline.WARNING: mb_strtoupper(): Passing null to parameter #1 ($string) of type string is deprecated in /app/vendor/laravel/framework/src/Illuminate/Support/Str.php on line 787 

Most of the time it's easy to fix those deprecations just by navigating to that file/line. But that's not always the case. For example, Str::* functions are very popular and it gets pretty difficult to debug where an invalid null argument is coming from, as there are usually thousands of calls throughout the project & vendors.

It'd be great for deprecations to be treated as non-critical errors. The whole patch would look something like this:

with($logger->channel('deprecations'), function ($log) use ($message, $file, $line) {
-    $log->warning(sprintf('%s in %s on line %s',
-        $message, $file, $line
-    ));
+    $log->warning((string) new ErrorException($message, 0, E_DEPRECATED, $file, $line));
});