Should we offer support to override automatic pagination? (auto_next_page_traversal)

It may be desirable to allow outside developers using the Mvault class to override the automatic pagination behavior in most GET calls.

Consider Changing: (example)

    // get the membership list activated
    // https://docs.pbs.org/display/MV/Membership+Vault+API#MembershipVaultAPI-listactivated
    public function getMembershipListActivated()
    {
        $uri = "memberships/filter/activated/";
        return $this->getResponseObjects('GET', $uri);
            //return $this->getClient()->request('GET', $uri);
    }

to something like this:

    // get the membership list activated
    // https://docs.pbs.org/display/MV/Membership+Vault+API#MembershipVaultAPI-listactivated
    public function getMembershipListActivated($auto_paginate = true)
    {
        $uri = "memberships/filter/activated/";
        if ($auto_paginate) return $this->getResponseObjects('GET', $uri);
        return $this->getClient()->request('GET', $uri);
    }

This would give them the ability to handle pagination of data manually in case they required it. (For example: With too many members in the mvault database the auto_paginated data set maybe too large and increase wait times.