Add option to sort Pipeline Schedules

• 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

What does this MR do and why?

Add option to sort Pipeline Schedules

Pipeline Schedules can now be sorted by ID, description or next_run_at in the UI and in GraphQL.

partially related to #37246

MR acceptance checklist

Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

Before	After

Database Changes

Base query

SELECT "ci_pipeline_schedules".* FROM "ci_pipeline_schedules" WHERE "ci_pipeline_schedules"."project_id" = 3 ORDER BY ci_pipeline_schedules"."id" DESC LIMIT 51

Modified according to sort order:

SELECT "ci_pipeline_schedules".* FROM "ci_pipeline_schedules" WHERE "ci_pipeline_schedules"."project_id" = 3 ORDER BY "ci_pipeline_schedules"."id" ASC LIMIT 51
SELECT "ci_pipeline_schedules".* FROM "ci_pipeline_schedules" WHERE "ci_pipeline_schedules"."project_id" = 3 ORDER BY "ci_pipeline_schedules"."description" ASC, "ci_pipeline_schedules"."id" DESC LIMIT 51
SELECT "ci_pipeline_schedules".* FROM "ci_pipeline_schedules" WHERE "ci_pipeline_schedules"."project_id" = 3 ORDER BY "ci_pipeline_schedules"."description" DESC, "ci_pipeline_schedules"."id" DESC LIMIT 51
SELECT "ci_pipeline_schedules".* FROM "ci_pipeline_schedules" WHERE "ci_pipeline_schedules"."project_id" = 3 ORDER BY "ci_pipeline_schedules"."ref" ASC, "ci_pipeline_schedules"."id" DESC LIMIT 51
SELECT "ci_pipeline_schedules".* FROM "ci_pipeline_schedules" WHERE "ci_pipeline_schedules"."project_id" = 3 ORDER BY "ci_pipeline_schedules"."ref" DESC, "ci_pipeline_schedules"."id" DESC LIMIT 51
SELECT "ci_pipeline_schedules".* FROM "ci_pipeline_schedules" WHERE "ci_pipeline_schedules"."project_id" = 3 ORDER BY "ci_pipeline_schedules"."next_run_at" ASC, "ci_pipeline_schedules"."id" DESC LIMIT 51
SELECT "ci_pipeline_schedules".* FROM "ci_pipeline_schedules" WHERE "ci_pipeline_schedules"."project_id" = 3 ORDER BY "ci_pipeline_schedules"."next_run_at" DESC, "ci_pipeline_schedules"."id" DESC LIMIT 51
SELECT "ci_pipeline_schedules".* FROM "ci_pipeline_schedules" WHERE "ci_pipeline_schedules"."project_id" = 3 ORDER BY "ci_pipeline_schedules"."created_at" ASC, "ci_pipeline_schedules"."id" DESC LIMIT 51
SELECT "ci_pipeline_schedules".* FROM "ci_pipeline_schedules" WHERE "ci_pipeline_schedules"."project_id" = 3 ORDER BY "ci_pipeline_schedules"."created_at" DESC, "ci_pipeline_schedules"."id" DESC LIMIT 51
SELECT "ci_pipeline_schedules".* FROM "ci_pipeline_schedules" WHERE "ci_pipeline_schedules"."project_id" = 3 ORDER BY "ci_pipeline_schedules"."updated_at" ASC, "ci_pipeline_schedules"."id" DESC LIMIT 51
SELECT "ci_pipeline_schedules".* FROM "ci_pipeline_schedules" WHERE "ci_pipeline_schedules"."project_id" = 3 ORDER BY "ci_pipeline_schedules"."updated_at" DESC, "ci_pipeline_schedules"."id" DESC LIMIT 51

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

1. navigate to http://127.0.0.1:3000/gitlab-org/gitlab-shell/-/pipeline_schedules
2. create some schedules
3. use the sort control to change order