Model options used for pagination and other common tasks for endpoint calls

[ggalmazor]

Other DNSimple API clients provide specific models for common tasks such as defining pagination parameters. We should have those in this client to avoid having to directly deal with maps and reduce the chance for accidental errors due to typos in key names or data types.

This issue should probably be combined with a review of the arg types of all endpoint methods using the Go client as a baseline, although I would suggest a deviation on the ID args that we know positively that are numbers, which in the Go client are String. I propose we use Long to make our output data classes interoperable with API calls as in: get account and use the account object to update the account without requiring to cast or transform values.