[5.5] Ignore select bindings while building update query

[themsaid]

The test with this PR shows an example of a sub select query using the default withCount model property, but this basically affects every sub select query.

When building the update query, we use where and join bindings but we don't use the select bindings, so any leftovers in this select binding will be used by the final query even though the final query doesn't need it, which will cause incorrect order of bindings.

This PR fixes the following issue: #20640

[brunogaspar]

Can this be ported to 5.4? The bug is very present there and was reported for 5.4 on #20640