fix(collection): widen filter/reject for Laravel 13 compatibility

[agissept]

Why

Spatie\BladeX\Laravel\Collection overrides filter(?Closure $callback = null) and reject($callback) with signatures narrower than the base Illuminate\Support\Collection. That's fine against the current 4.2-era base, but the L42x → Laravel 13 upgrade changes the base to:

• filter(?callable $callback = null)
• reject($callback = true)

PHP's LSP forbids a child from narrowing a parameter type or making an optional parameter required, so under L13 both overrides become a fatal error at class load:

Declaration of Spatie\BladeX\Laravel\Collection::filter(?Closure $callback = null)
must be compatible with Illuminate\Support\Collection::filter(?callable $callback = null)

What

Widen both overrides to the least-restrictive form that is compatible with both the current base and the Laravel 13 base:

method	before	after
filter	filter(?Closure $callback = null)	filter($callback = null)
reject	reject($callback)	reject($callback = true)

• filter → untyped. PHP does not accept callable as a widening of Closure (verified: ?callable overriding Closure is itself a fatal). Dropping the type (mixed) is the only signature that is a valid override against both filter(Closure) (4.2) and filter(?callable) (L13).
• reject → = true default, so it's no longer stricter than either base.

Method bodies are unchanged — they already implement the ARRAY_FILTER_USE_BOTH value+key semantics, so behaviour is identical on both bases.

Compatibility

Verified against both bases:

• 4.2 base (filter(Closure), reject($callback)) — loads (child widens).
• Laravel 13 base (filter(?callable), reject($callback = true)) — loads + filter/reject return correct results.

This means the fix can be merged and deployed now, independently of the framework upgrade — no lockstep required.

🤖 Generated with Claude Code