ExpireBuildArtifactsWorker query builds table without ordering enqueuing one job…

Paco Guzman requested to merge 23096-expire-artifacts-per-job into master

What does this MR do?

Avoid ordering ci_builds table by id which is not performant. Besides we enqueue one job per ci_build we need to expire.

I've used Sidekiq::Client to avoid roundtrips when inserting a bunch of jobs

Are there points in the code the reviewer needs to double check?

Why was this MR needed?

See #23096 (closed)

Screenshots (if relevant)

Does this MR meet the acceptance criteria?

What are the relevant issue numbers?

Closes #23096 (closed)

Merge request reports