[10.x] Fix RateLimiter callback return substitution (#44820)

[a-bashtannik]

This breaking update allows users to control return values explicitly without converting to boolean and fixes the substitution of false with true.

Bug description:

The RateLimiter::attempt method contains ?: operator and casts the return value of $callback function to true for all list of values considered as false.

    public function attempt($key, $maxAttempts, Closure $callback, $decaySeconds = 60)
    {
        if ($this->tooManyAttempts($key, $maxAttempts)) {
            return false;
        }

        return tap($callback() ?: true, function () use ($key, $decaySeconds) {
            $this->hit($key, $decaySeconds);
        });
    }

Steps To Reproduce:

$return = RateLimiter::attempt('key', 10, fn() => false, 1); // $return = true, not false

$return = RateLimiter::attempt('key', 10, fn() => [], 1); // $return = true, not []
$return = RateLimiter::attempt('key', 10, fn() => 0, 1); // $return = true, not 0
$return = RateLimiter::attempt('key', 10, fn() => 0.0, 1); // $return = true, not 0.0
$return = RateLimiter::attempt('key', 10, fn() => "", 1); // $return = true, not an empty string

// etc.

Case: 3rd-party APIs may return empty arrays as a successful response.

Brings backward incompatibility to those who depend on true return.

[cheros989]

We had a problem already because attempt returns not exact value you return from closure. It does cast! But from the documentation it SHOULD return exactly the value you return from closure (3d parameter).