feat(ci): add more flags to filter ci list output

• Please check this box if this contribution uses AI-generated content (including content generated by GitLab Duo features) as outlined in the GitLab DCO & CLA. As a benefit of being a GitLab Community Contributor, you receive complimentary access to GitLab Duo.

Description

Add more flags for ci list command.

Related Issues

Resolves #7713 (closed)

How has this been tested?

I've run glab ci list against a gitlab repo that has a large number of pipelines and confirmed that including new flags filters the list of ci pipelines as expected.

Some examples:

$ glab ci list --source merge_request_event --per-page 3
Showing 3 pipelines on [redacted]. (Page 1)

(success) • #1588596729  (#75830)  refs/merge-requests/2635/head   (about 1 day ago)
(failed) • #1588407881   (#75827)  refs/merge-requests/2636/merge  (about 1 day ago)
(success) • #1588364837  (#75819)  refs/merge-requests/2635/merge  (about 1 day ago)

$ glab ci list --scope tags                             
Showing 1 pipeline on [redacted]. (Page 1)

(failed) • #842767445  (#24747)  [redacted]-0.0.1  (about 1 year ago)

$ glab ci list --username bradymitch --per-page 5 --sort desc
Showing 5 pipelines on [redacted]. (Page 1)

(success) • #1586662185  (#75721)  refs/merge-requests/2632/merge  (about 2 days ago)
(success) • #1586657095  (#75715)  fixPermissions                  (about 2 days ago)
(success) • #1586469522  (#75615)  fixPermissions                  (about 3 days ago)
(failed) • #1584613316   (#75382)  [redacted]                      (about 4 days ago)
(failed) • #1583074718   (#75290)  [redacted]                      (about 4 days ago)

Screenshots (if appropriate):

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation
• Chore (Related to CI or Packaging to platforms)
• Test gap