@pushrbx New commits attempt to resolve the repeating of code by refactoring the way the scraper is used and parameters are validated. The implementation could be the starting+testing point for this PR before we put this elsewhere.

I've introduced a QueryResolver class for handling queries that will be passed into the scraper instance. It includes a validation layer with ValidationTypeEnum being the first of its type. It also accepts a custom exception to throw in the event the validation fails. Validation is optional and in this case, is only used for sort.

ScraperHandler bootstraps the QueryResolver along with the getter function name and the respective request object (thanks for the example code!). There are instances where the name of the request class could differ from the getter function of the scraper. So we need to provide their values separately.

A util method, getSerializedJSON(), is also present in ScraperHandler to convert the response object into a serialized JSON.

Let me know what you think.