[13.x] Make between()/unlessBetween() independent of timezone() call order

[ManicardiFrancesco]

The problem

between() / unlessBetween() evaluate the timezone eagerly, the moment the method is called. So the result silently depends on where timezone() sits in the chain:

// ✅ uses Europe/Rome
$schedule->command('foo')->timezone('Europe/Rome')->between('10:00', '12:00');

// ❌ silently uses the previous timezone (e.g. UTC) — task runs at the wrong hour
$schedule->command('foo')->between('10:00', '12:00')->timezone('Europe/Rome');

Why this is a bug, not user error

between() / unlessBetween() are the only frequency methods whose outcome changes with call order. Every other one is order-independent: testBasicCronCompilation already asserts "chained rules should be commutative". This PR brings these two in line with that existing guarantee.

The fix

Defer the time-interval computation into the filter closure, so $this->timezone is read when the filter runs rather than when it's defined. The two forms above become equivalent.

• No public API change, ~minimal diff.
• No behavioral change for chains that were already in the "lucky" order.
• The schedule is defined and evaluated within the same schedule:run, so moving Carbon::now() into the closure doesn't change timing.

Regression test (testTimeBetweenChecksTimezoneCallOrder) covers both between() and unlessBetween() in both chaining orders.

[taylorotwell]

Agent review:

Should fix — src/Illuminate/Console/Scheduling/ManagesFrequencies.php:60 recomputing Carbon::now() on every filter invocation changes behavior for repeatable sub-minute events because filtersPass() is called throughout the minute, so windows like everySecond()->between('10:00', '10:00') can pass only at the first second instead of remaining consistent for the schedule:run.

[ManicardiFrancesco]

Fixed ^ : we capture the comparison instant once when the filter is defined (i.e. once per schedule:run), while still reading $this->timezone lazily inside the closure. This restores the original frozen-instant behavior for sub-minute events and keeps the call-order independence (timezone() after between()) that this PR introduced.