[5.6] Let Exception Handler do the reporting

[deleugpn]

When using the API Guard on auth.php, Laravel will try to authenticate the user through the Authorization Header.
The User Provider can be Eloquent, in which case it will require a valid database connection.

The problem happens when the database connection configuration is wrong (username, password, database, etc) and the Auth Provider tries to reach for the database to authenticate the User.
Since the database is wrong, an exception will be thrown. However, the Handler will try to load the Context from the Auth Guard as stated here: https://github.com/laravel/framework/blob/5.6/src/Illuminate/Foundation/Exceptions/Handler.php#L151-L153.

The Auth Guard will try to reach for the Database to load the User, which again will throw an exception, which will try to load the Context, which will go to the Database until PHP Max Allowed Memory gets exhausted.

This pull request changes the ConnectionFactory to just rely on the default Exception Handler instead of trying to force-log an exception itself, thus avoiding an infinite loop.

[sisve]

Does this fix #23415? Will this be backported to 5.5?

[GrahamCampbell]

This test is totally broken if you don't happen to have a copy of mysql running on your local machine!

[GrahamCampbell]

I'll PR a fix.