[13.x] Preserve falsey concurrency exception parameters

[Amirhf1]

The Problem

When a concurrent task fails while using the ProcessDriver, the framework captures the exception in the child process, serializes it, and reconstructs it in the parent process.

However, during the reconstruction process in ProcessDriver.php, the driver uses array_filter() without a callback to check if custom constructor parameters were captured:

...(! empty(array_filter($result['parameters']))
    ? $result['parameters']
    : [$result['message']])

Because PHP's default array_filter strips out all falsey values, legitimate arguments like 0, false, or "" (empty string) are treated as completely absent. As a result, the framework incorrectly falls back to passing the exception's string message into the constructor instead of the actual arguments.

If you throw a custom exception that expects a falsey integer or boolean value:

class RetryAfterException extends Exception
{
    public function __construct(public int $seconds)
    {
        parent::__construct("Retry after {$seconds} seconds.");
    }
}

Concurrency::run([
    fn () => throw new RetryAfterException(0),
]);

The 0 parameter is discarded because it's falsey. When the driver attempts to reconstruct the exception, it passes the string message into the constructor instead of the integer 0, which immediately crashes the application with a TypeError.

After this PR

The reconstructed exception faithfully retains its original constructor parameters:

// Works perfectly now:
$exception->seconds; // 0

The presence check now explicitly filters out only null values. Valid non-falsey parameters remain unaffected, and the message fallback still cleanly handles cases where no constructor parameters could be captured at all.