Schedule async index build for ci_job_artifacts

Our purpose-built index for removal of expired records from
ci_job_artifacts does not exclude artifacts where expire_at is null.
This means job traces, which get unlocked but have no expiration, are
polluting an index that would otherwise be a clean ready-for-removal
queue and much smaller.

Changelog: performance