Add isNowOrFuture() and isNowOrPast() methods

[AndrewMast]

Why

Laravel recently introduced relative date shorthands to the Query Builder (laravel/framework#54408). Some of these methods include wherePast and whereFuture. Along with these methods, whereNowOrPast and whereNowOrFuture were introduced. These have been really helpful when querying timestamps.

However, after using these new query methods, I keep finding myself reaching for $carbon->isNowOrPast() and $carbon->isNowOrFuture(), but they don't exist in Carbon. I would have assumed something like this would have been implemented in Carbon already.

After a bit of digging, I found that isPast used to be inclusive in that it was an inverse of isFuture and would be true for the current time. This was fixed more than 10 years ago in briannesbitt/Carbon#142, and rightly so. However, I would like to bring back a bit of this functionality in two new methods.

What

Added the following methods:

• isNowOrFuture: Copied isFuture but changed greaterThan to greaterThanOrEqualTo
• isNowOrPast: Copied isPast but changed lessThan to lessThanOrEqualTo

Added tests in both tests/Carbon/IsTest.php and tests/CarbonImmutable/IsTest.php based on existing isFuture and isPast tests.

[AndrewMast]

I see that I am getting a "merging is blocked" error. Should I have opened this on briannesbitt/Carbon?

Also on a side note, what is the recommended way to ensure our code matches the current style and passes the tests? Because the composer script for phpunit fails due to --verbose (apparently PHPUnit 10 removed the flag?), composer phpcs on a fresh clone finds a ton of formatting changes, and composer phpdoc adds #[ReturnTypeWillChange] to the createFromTimestamp method.

[kylekatarnls]

I see that I am getting a "merging is blocked" error. Should I have opened this on briannesbitt/Carbon?

Nope, it's the same on the other repo, merging is blocked as long as test didn't complete and pass, and a first approval is needed to run the tests on GitHub Actions.