[SPIKE] Determine how to implement pagination when fetching co-op reviews

[joshw2048]

FYI: A spike is an agile term referring to a ticket designed purely for research.

Right now, when we fetch co-op reviews, we get them all back in one big object. This is bad because imagine if we have millions of reviews and fetch them every single time. Pagination is the solution - it lets us get a certain amount of records (say, 20) at a time.

This ticket will kick us off on your project for the semester.

Acceptance Criteria:

• speak to Rishi about how we currently fetch reviews with our API
• understand pagination and decide on what approach we what (cursor vs offset vs ???)
• speak to Josh about follow-on tickets to actually implement pagination