Fix pagination being ignored for Gitea

[CirnoT]

Fixes #64

Gitea implementation was completely ignoring opts from Drone, so after we introduced proper pagination headers in v1.12, Drone would ask go-scm for page 2, and go-scm would request page 1 and return it, causing infinite loop of requests.

[moepman]

Sorry for being slightly off-topic here, but my go skills are not good enough to tell it to use your patch when building drone. If you could give me a pointer how to achieve that I'd like to rebuild drone and report back if this actually fixes go-gitea/gitea#11970

[paulbsd]

Hi,

On your commit, there're mentions to "per_page" parameters but on the Gitea API version 1.12.0, per_page doesn't exists, and may be replaced by "limit".

Paul

[CirnoT]

Ah sorry @paulbsd didn't notice that when copying util file from github implementation

[CirnoT]

@moepman Before building drone you need to go get new version of go-scm.

[CirnoT]

@bradrydzewski I've went ahead and added support for pagination on every endpoint. I do not guarantee that all of them support pagination right now, but If i am right then it won't matter anyway because Drone will never ask go-scm for next page if Link header is not present.

[moepman]

@moepman Before building drone you need to go get new version of go-scm.

I still didn't quite figure out how to tell go get use your branch instead of upstream...
However: putting the contents of CrinoT/patch-1 inside go/pkg/mod/github.com/drone/go-scm@v1.6.1-0.20200417160414-b3466885f96 and then running go install github.com/drone/drone/cmd/drone-server resulted in a drone-server binary that would correctly display all of my 33 repositories from my gitea 1.12 installation :)
So I can confirm that this should fix the issue.