Add dump method to Query\Builder class

[morrislaptop]

Inspired by #19755

This PR adds a dump method to Illuminate\Database\Query\Builder so you can easily debug multiple spots in a query builder chain.

$users = DB::table('users')
           ->select('name', 'email as user_email')
           ->join('contacts', 'users.id', '=', 'contacts.user_id')
           ->union($first)
           ->dump()
           ->where('something', 'true')
           ->orWhere('name', 'John')
           ->orderBy('name', 'desc')
           ->groupBy('account_id')
           ->dump()
           ->offset(10)
           ->limit(5)
           ->having('account_id', '>', 100)
           ->get();

[Dylan-DPC-zz]

Do check #21796.

[morrislaptop]

@Dylan-DPC I had a feeling that would be a bit much, what about just the dump() method?

[Dylan-DPC-zz]

Actually was pointing more towards Taylor's comment at the bottom (forgot to link the comment).

[morrislaptop]

Oh right, I'm referencing #19755 as Collection::dump() was possible through a macro (and was implemented that way in the spatie/laravel-collection-macros repo until it was merged into core).

I'm guessing having this in core would be useful for the developer experience as it follows the same pattern as elsewhere in the framework.

I guess it will be up to @taylorotwell to decide?

[sisve]

I'm strongly against this change (and the Collection::dump()) too. If we continue this path every object in the framework will soon have a dump() method.

[taylorotwell]

No plans on adding. You can macro it.

[morrislaptop]

Ok, for anyone else who finds this thread, the macro is available at https://github.com/morrislaptop/laravel-query-builder-dump