Fix for pagination issues in GitLab list repositories

[gineshkumar]

• All tests passed. If this feature is not already covered by the tests, I added new tests.
• I used go fmt ./... for formatting the code before submitting the pull request.
• This feature is included on all supported VCS providers - GitHub, Bitbucket cloud, Bitbucket server, and GitLab.

---

Issue Description-

Gitlab List Repositories do not iterate through all the pages in the remote repository. This is because the "X-Total-Pages" are not populated by the remote API, which the library uses to decide whether to continue iteration or not.

Library requests for all projects the current user have visibility; this is similar to browsing "Explore Projects" (https://gitlab.com/explore/projects) in Gitlab. For performance reasons, if a query returns more than 10,000 records, GitLab doesn’t return the following headers:

• x-total.
• x-total-pages.
• rel="last" link.
  https://docs.gitlab.com/ee/user/gitlab_com/index.html#pagination-response-headers

"X-Total-Pages" is available if you request "membership=true" projects; these are the projects where the current user is a member.

Fix -

• vcsclient/gitlab.go - added membership=true to the request URI.

• vcsclient/gitlab_test.go - Updated the test case, to mock pagination.

• vcsclient/testdata/gitlab/projects_response.json - Added more data to return two pages, with a default page size of 20.

[yahavi]

Thanks for this important bug fix, @gineshkumar!