Pagination logic depends only on hasNextPage, but should also consider endCurso for GraphQL requests. #2130
Description
When a request is made in GraphQL that includes endCursor but not hasNextPage, we do not correctly apply the logic that is needed to determine when we are in a pagination scenario. This causes endCursor to not be populated correctly, such that even though we are on the last page of records, we will have a non-null endCursor.
Related to #2030
where we are getting the same inconsistent behavior as the issue above, but simply for the case where only endCursor is included in the request.