Allow specifying "criticality" (log level) per exception

[aedart]

PSR-3 offers several criticality levels. It would be really nice, if the current \Illuminate\Foundation\Exceptions\Handler could make it easier to utilize per exception.
After all, some exceptions are more critical than others - if at all critical.

This could be as easy as stating an array, containing the exception's namespace as the key, and a log level as the value.

Example

use Psr\Log\LogLevel;

// ...Inside the exception handler
$logLevels => [
    \Acme\Flights\Exceptions\FlightNotRecordedException::class => LogLevel::CRITICAL
];

The name of the class property is not well considered, in the shown example - nor is it that important, in this context.

Default Behavior

Unless a custom criticality level is specified for the current caught exception, then it should just be logged as LogLevel::ERROR (current behavior of Laravel's default exception handler). Logging must of course continue to respect the current $dontReport behavior, ...etc.

Workaround

In the current Laravel version, developers need to make use of reportable() mechanism, perform desired logging, and stop the propagation, to avoid the default logging from creating a dual entry.
Alternatively, developers must overwrite the report() method and customize it.
Both alternative approaches are doable. But, it is a bit cumbersome.

The proposed solution SHOULD NOT break any current functionality of the default exception handler (at least none that I can think of).