Use IntegerRangeType for pagination schema fields

[hosni]

Hi @romalytvynenko

After v0.13.0, Scramble supports ranged integer types via IntegerRangeType.
It would be great to use this new type for pagination-related schemas to make their definitions more accurate.

Currently, pagination fields like per_page, current_page, from, to, last_page, and total are defined as plain IntegerType.
Some of these fields can be null (and Scramble already handles that correctly), but their numeric ranges are not currently constrained.

Proposal

Use IntegerRangeType to define the lower bounds for these pagination fields:

Field	Suggested Type
per_page	new IntegerRangeType(min: 0)
current_page	new IntegerRangeType(min: 1)
from	new IntegerRangeType(min: 1)
to	new IntegerRangeType(min: 1)
last_page	new IntegerRangeType(min: 1)
total	new IntegerRangeType(min: 0)

(Fields like from and to can still be nullable, this suggestion only concerns their non-null range.)

Why

• Reflects the actual constraints of Laravel-style pagination responses.
• Prevents negative numbers in generated schemas.
• Improves OpenAPI documentation accuracy and validation precision.
• Leverages the new IntegerRangeType introduced in PR #996.

This would make the generated API documentation both stricter and semantically correct.

[romalytvynenko]

@hosni cool! Feel free to submit a PR

[hosni]

Thanks! I'll submit a PR in the next hour.

[hosni]

@romalytvynenko, I submitted a PR for this: #1018