Stack overflow in _paginate_response method

[Disruption]

The _paginate_response method in the client performs pagination via recursion:

• You call and endpoint, which calls _get, which calls _paginate_response, which on a while loop calls _get, which calls _paginate_response, etc

There are a few problems with this approach:

• If the collection being requested is very big, and the page size is the default (10 items) this can lead to hundreds of stacked calls, and ultimately an exception will be raised
• If we hit a faulty response (i.e. one where response.data is not a dict instance, which is one of the conditions for just returning response, that return will come inside the while loop, and we will do response.data["value"] += data, but if we reach through that path, response.data is not a dict, so response.data["value"] might fail if data is not a subscriptable object.

This could be solved by calling self._request directly on the while loop inside the _paginate_response method, rather than _get, which eliminates recursion. The check for response.data being a dict instance should be performed there as well to avoid the potential exception.

[ingmferrer]

Hello, I appreciate if you can send a PR solving this, since you're reproducing the error.

[Disruption]

@ingmferrer Sure, I will do a PR with the fix after #27 is merged, since both fixes are exactly on the same line of code

[Disruption]

Fixed in #28