[10.x] Binding order is incorrect when using cursor paginate with multiple unions with a where

[thijsvdanker]

When using cursorPaginate on a query that has multiple unions with their own where clause, the binding order is incorrect.

This happens because:

https://github.com/laravel/framework/blob/11.x/src/Illuminate/Database/Concerns/BuildsQueries.php#L436
adds the bindings for the cursor where to the end of the bindings and not in the position that they should be.

The result is a query that binds the wrong values to the wrong parameters in the query.

This PR recreates the union bindings in the cursor paginate logic so that the cursor where binding is in the correct position.

This PR is similar to #50810 but does not change the structure of the union binding to address the fear of a breaking change.
Instead it is only applied in the context of cursor pagination.

[taylorotwell]

I dunno - if the bindings were being duplicated this PR was already apparently broken? Why did the tests not show that? It shakes my confidence in merging 😅

[thijsvdanker]

Yeah I agree that that doesn't look too solid.
I'll see if I can make test that covers that piece of code.

[thijsvdanker]

I've given each builder its own variable name to make it a little bit easier to see what's going on.
b512794

[driesvints]

@thijsvdanker please mark this as ready if you need another review.

[thijsvdanker]

I've added an Eloquent test that demonstrates the issue: 3e87617

[crynobone]

I've added an Eloquent test that demonstrates the issue: 3e87617

Can confirm the usage will be broken via #51076