[5.8] Fix for container app()->call() method

[imanghafoori1]

Addresses these issues :
#26851
#22687
#26837

Following my previous bug fix #26852 which caused a new nasty bug and eventually got reverted...
I created an other PR to add the missing tests to cover more cases #26897

Now I am coming up with an other solution for making it really fixed.

[laurencei]

There are a bunch of changes in this PR that are not related to your change.

For example, there are styling changes, the adding of function return types to functions you have not changed etc (I dont think we use those in the framework either, but I could be wrong).

To increase the changes of your PR been accepted by Taylor the PR should only contain changes directly related to what you are changing. Otherwise it makes the PR very big and difficult to see what actual code changes are been done.

[imanghafoori1]

Some changes are accidentally made by IDE.
But this fix required a lot of change in the logic.
I try to provide enough comments, meaningful variable names and unit test to be clear.

Anyway this is a work in progress and still requires a lot more consideration.

[mfn]

Thanks for the PR, I like it 👍

[driesvints]

@imanghafoori1 sorry, the Github GUI showed me some rebase notices but those turned out to be unrelated of conflicts.

[imanghafoori1]

It seems the ContainerTest.php file needs to be split apart into more files, each covering one specific feature. I do not know whether it is against any convention or not.
(For Example all the tests covering the app()->call() should reside in one file.)

[taylorotwell]

No plans to merge this implementation.

[imanghafoori1]

Ok, hope I have manged to provide something that can be inspired from in future.

[imanghafoori1]

@taylorotwell
I see that if this issue gets fixed, then laravel can use $app->call(... in the base facade class to call the underlying implementation of facades.

This means that the end user can enjoy the automatic method injection when using real-time facades.