[8.x] Throw ModelNotFoundException for sole in Eloquent

[rodrigopedra]

Follow up to #35869

As suggested in comment #35869 (comment) by @taylorotwell , this PR throws a ModelNotFoundException when ->sole() is called from an Eloquent Query Builder and no records are found.

This is particularly useful as ModelNotFoundException exceptions are handled automatically in HTTP requests by returning a 404 response.

Maybe we should also add some kind of HTTP handling for the MultipleRecordsFoundException when called from an Eloquent Query Builder.

[themsaid]

I think this is going to make things a bit confusing, you'll need to account for ModelNotFoundException and RecordsNotFoundException in your code based on wether the instance is a base builder or eloquent builder.

I think having RecordsNotFoundException associated with the sole() method makes it easier.

What we can do is make ModelNotFoundException extend RecordsNotFoundException.

[rodrigopedra]

Making it extend RecordsNotFoundException is a good idea, but won't make the HTTP handler return a 404.

I can instead of extending it on an Eloquent builder add an if clause to the Illuminate\Foundation\Exceptions\Handler@prepareException to account for a RecordsNotFoundException.

What do you think?

[rodrigopedra]

My bad, now I get what you meant from your first message.

Updated to extend from RecordsNotFoundException. Thanks!

[rodrigopedra]

I suggest returning a 400 Bad Request for a MultipleRecordsFoundException, but I'll leave it up for discussion.