[8.x] The use of whereHasMorph in a whereHas callback generates a wrong sql statements

[selcukcukur]

The use of whereHasMorph in a whereHas callback generates a wrong sql statements. The reason for this is that it cannot capture the "where" part correctly during parsing in the "hasMorph" method.

One thing to be aware of is that if this is a situation that occurs only in very complex queries, it may be possible to spoil something that is going well. Although the correction I applied allows it to do the same thing correctly, we cannot see if it will cause errors at the extreme points without trying.

I believe we should look at what endpoints create a problem or not by implementing this PR. It should not be forgotten that there is a possibility that it will not cause any problems.

[BrandonSurowiec]

Need to add a test to prove the fix. :)

[selcukcukur]

Need to add a test to prove the fix. :)

It is not a pull request that basically changes the way it works. Already existing test files should have already indicated when there was a problem. Everything seems to be fine. But I will of course prepare and include it in the test files that I will take a look at at a convenient time if they need to be added.