Fix: Improve validateInteger ergonomics and fix BC break

[ntm-dev]

This pull request addresses a breaking change from PR #56503 and improves the ergonomics of the validateInteger method.

The signature for validateInteger was updated in v12.22.0, introducing a new mandatory $parameters argument. This caused an ArgumentCountError for the common pattern of calling this method directly within a custom validation Closure, breaking backward compatibility.

Beyond just fixing the regression, this PR also improves the developer experience. Forcing developers to pass an empty array ([]) for the most common use case (a simple integer check without strict mode) adds unnecessary verbosity to the code.

An API should be simple for common tasks. By making the $parameters argument optional, we restore the previous behavior and also create a cleaner, more intuitive method call.

Before (in v12.22.0+ to avoid error):

$validator->validateInteger($attribute, $value, []); // Unnecessary empty array

After this PR:

$validator->validateInteger($attribute, $value); // Clean and concise

Solution
This PR makes the $parameters argument optional by providing a default empty array. This change is completely backward compatible, fixes the breaking change, and simplifies the API for its primary use case, without affecting the new strict functionality.

- protected function validateInteger($attribute, $value, array $parameters)
+ protected function validateInteger($attribute, $value, array $parameters = [])