AO3-5984 Add max-min limits to int range searches

[techlingyi]

Pull Request Checklist

• Have you read "How to write the perfect pull request"?
• Have you read the contributing guidelines?
• Have you added tests for any changed functionality?
• Have you added the Jira issue number
  as the first thing in your pull request title (e.g. AO3-1234 Fix thing)
• Do you have fewer than 5 pull requests already open? If not, please wait
  until they are reviewed and merged before creating new pull requests.

Issue

https://otwarchive.atlassian.net/browse/AO3-5984

Purpose

Adds an MAX_SEARCH_INT_RANGE: 2000000000 constant to config/config.yml and clamps all int-range searches (including num, <num, >num, and num1-num2) within the range 0 to MAX_SEARCH_INT_RANGE.

Since int ranges are all handled by the same function, this does go beyond the ticket for word count to also affect searches on hits count, kudos count, etc., but these statistics are also stored in MySQL int columns and so should also have the same maximum search limit. (They currently experience the same 500 error that word count does with numbers that are too large.)

Testing Instructions

(already touched on in the Jira issue but for the sake of completeness)

• use all range search operators mentioned above in https://archiveofourown.org/works/search for the Word Count field, and ideally the Hits/Kudos/Comments/Bookmarks fields as well
• pick any tag and use all range search operators mentioned above in the "Search within results" field of the Sort and Filter sidebar (e.g. ‵words:>10000000000000000000`; ideally test the hits, kudos, comments, bookmarks keywords as well)
• pick any tag and activate the Word Count dropdown to fill in the From and To fields, one at a time and then both

Credit

Ling-Yi (any pronouns)