Use BindingResolutionException to signal problem with container resolution (#32349)
Use BindingResolutionException to signal problem with container resolution (#32349)

As part of static analysis sometimes abstracts get resolved which aren't
resolvable => that's totally fine but it would help to use a common
exception to signal this.

I figured BindingResolutionException would be the correct one. For example,
it's caught in cases like `\Illuminate\Foundation\Exceptions\Handler::whoopsHandler`
and IMHO this would also benefit from a streamlined exception.
dwightwatson/framework,lucasmichot/framework,mul14/laravel-framework,JamesForks/framework,cybercog/framework,vlakoff/framework,JosephSilber/framework,hafezdivandari/framework,notebowl/laravel-framework,ChristopheB/framework,mul14/laravel-framework,stevebauman/framework,arturock/framework,driesvints/framework,vlakoff/framework,ChristopheB/framework,leo108/laravel_framework,cybercog/framework,lucasmichot/framework,laravel/framework,leo108/laravel_framework,dwightwatson/framework,morrislaptop/framework,mul14/laravel-framework,stevebauman/framework,samlev/framework,vlakoff/framework,JamesForks/framework,tjbp/framework,tjbp/framework,tomschlick/framework,notebowl/laravel-framework,hafezdivandari/framework,halaei/framework,driesvints/framework,arturock/framework,crynobone/framework,tomschlick/framework,arturock/framework,crynobone/framework,ChristopheB/framework,samlev/framework,morrislaptop/framework,bytestream/framework,cybercog/framework,tomschlick/framework,halaei/framework,bytestream/framework,tjbp/framework,halaei/framework,laravel/framework,mul14/laravel-framework,JosephSilber/framework