Fix NoMethodError with tampered params

[excid3]

I've had some requests come in that are clearly messing with params such as ?page[]=2 and ?page[testing]=1

This causes an error when casting to_i here since page is an Array or Hash and not a String.

pagy/gem/lib/pagy/classes/request.rb

Line 24 in 53f6bbb

return [page.to_i, 1].max if force_integer

It raises a NoMethodError which isn't ideal to rescue from in a controller.

By casting to a String, this will fix the issue and return 0 when an invalid value is found since:

["2"].to_s.to_i #=> 0
{"testing" => "1"}.to_s.to_i #=> 0

This should make Pagy raise a lot less errors when the page param is tampered with by bots or malicious users.

[ddnexus]

Simple and effective! Thank you Chris.

[RyanTG]

Neat, thanks.

For some reason our bot visitors' favorite thing to do is include a second limit param that only contains a single quote. ?limit=50&limit=%27&page=15. Not exactly malicious. Just... strange and annoying.

[excid3]

That is annoying. limit could probably use the same treatment. Didn't even cross my mind yesterday.