[5.3] fix bindings on update statements with advanced joins for all grammars

[litvinchuk]

solution for issue #16367, #16363

[taylorotwell]

Needs full description of how fix addresses problem. Need for passing into this overriden prepareBindingsForUpdate method, etc.

[litvinchuk]

For different grammars, we need a different order for the bindings and values.

Example Mysql:
update users inner join orders on users.id = orders.user_id and users.id = ? set email = ?, name = ?
We need first set join parameters and then values

Example Postgres:
update "users" set "email" = ?, "name" = ? from "orders" where "users"."id" = "orders"."user_id" and "users"."id" = ?
We need first set values and then join parameters

That's why we need merge bindings and values in different way for each grammar

[themsaid]

@litvinchuk thank you, looks like the syntax for Postgres and SQL Server varies from MySQL, closing my other PR so that we can work on this one.

[taylorotwell]

Why did you change this unrelated code?

[litvinchuk]

Bindings are coming in raw format now, so the processing should be changed accordingly and can be simplified.

[taylorotwell]

In that case how will the check for isJsonSelector work? Since you say they are coming in with numeric keys? Won't $column always be an integer?

[litvinchuk]

Previously we were receiving merged bindings and checked isJsonSelector first count($values) of items from bindings, because values always were first and the keys were of integer type.
In this case we can check only values and then merge with bindings and the keys can be of any type.

[litvinchuk]

$column can be of any type, not only integer