Add PipelineListsOptions to woodpecker-go

[xoxys]

I fear that's a breaking change... It's a bit pain IMO that we can not version the go lib independent of the server.

I don't see a (good) way to make it non-breaking. If you have a better idea, please let me know. However, as this will be breaking anyway, we should replace all other raw query parameters used in the lib (e.g. https://github.com/woodpecker-ci/woodpecker/blob/main/woodpecker-go/woodpecker/repo.go#L6) by proper opt structs as well as this makes it easier to extend with future options.

Changes:

• Add PipelineListOptions and expose them to cli

❯ ./dist/woodpecker-cli pipeline ls --format "#{{ .Number }} {{ .Started }}" --before "2023-08-21T21:11:02+02:00" 2
#1 1692644861
❯ ./dist/woodpecker-cli pipeline ls --format "#{{ .Number }} {{ .Started }}" --after "2023-12-11T15:07:04+01:00" 2
#43 1702762952

• Add RepoListOptions and expose them to cli

❯ ./dist/woodpecker-cli repo ls --all
testorg/test (id: 2, forgeRemoteID: 3, isActive: true)
testorg2/test2 (id: 4, forgeRemoteID: 4, isActive: true)
woodpecker/woodpecker-test (id: 0, forgeRemoteID: 1, isActive: false)
testorg/woodpecker-test (id: 6, forgeRemoteID: 2, isActive: true)

• Add DeployOptions
• Add PipelineStartOptions
• Add PipelineLastOptions
• Add RepoPostOptions
• Add RepoMoveOptions

[xoxys]

How do we handle such PRs in general? Keep it open until we want to do a major version bump?

[qwerty287]

We actually just merged them and ignored that they're breaking...

[xoxys]

Maybe we should just move the lib to a dedicated repo? But same argumentation might apply to cli, agent etc. which would end in a repo mess instead of the current monorepo approach. So maybe a bad idea 🙃

[woodpecker-bot]

Deployment of preview was successful: https://woodpecker-ci-woodpecker-pr-3652.surge.sh