Handle magic calls on model and query builder correctly

[canvural]

Ok. This turned out to be a little bigger PR than I imagined 😅 But the outcome is good! I tested it on my big project. And I could go to level 4 from level 3 without changing anything.

List of changes:

• Model class' __call method is mimicked. If it's not increment or decrement calls are forwarded to \Illuminate\Database\Eloquent\Builder
• \Illuminate\Database\Eloquent\Builder __call method is mimicked. With one exception. Local macros are not supported. Otherwise, all unknown calls are forwarded to \Illuminate\Database\Query\Builder class. But return type is still \Illuminate\Database\Eloquent\Builder
• Added support for calling get on the query builder. This will return Collection class and elements of the collection correctly typehinted with the model.
• Return type of query builder methods is fixed. Previously User::where('foo', 'bar') was returning the model itself. See Wrong tests and possible wrong implementation #324 This is fixed now
• Return type of model local scopes is correctly handled now.
• Added correct return types for model retrieval and creation methods. Ex. find, firstOrCreate etc.
• Added more test cases for everything.

There might be an increased number of errors after these changes. But this is because there were false negatives before. For example Larastan would think User:whereFoo('bar')->someRelation() is a correct code and returning model instance. But that example is not a valid Laravel code in reality. So I guess any of this can't be considered as breaking change. And all the existing (which I didn't change) tests are passing, so existing functionality is preserved.

I'm open to any comments and questions. About implementation or other things.

[szepeviktor]

Too big to fail.

[nunomaduro]

This pull request is awesome. Congrats buddy! And thank you again for your work.

[canvural]

@nunomaduro Can we merge this and make a new 0.4.2 release? Or do you want this in a new release? 0.5 maybe ?

[szepeviktor]

@canvural Please do release v0.4.2

[canvural]

@nunomaduro Is there anything left to do here? Can we merge?

[nunomaduro]

LGTM

[canvural]

Ok, so it's up to you. We can't merge because of the continuous-integration/styleci/push Expected status. 🙄

[bobbybouwmann]

@nunomaduro Can we force merge this, since we're only waiting for the style ci?

[nunomaduro]

Done.

[bobbybouwmann]

@nunomaduro Do you have an ETA for the release? :D

[canvural]

I was thinking maybe we can test it a little, with dev-master in composer, and then make a release if everything seems fine.

But I can make the release 0.4.3, if it's ok with @nunomaduro

[spaceemotion]

I will try the changes as soon as I am able (still today). Will report back in the issues once I got around to it.

[bobbybouwmann]

Thanks for the awesome work guys!

[nunomaduro]

@bobbybouwmann Share some love RT @canvural his work: https://twitter.com/can__vural/status/1186564559261388800.