Add an `options` argument to `RunPipelineScheduleWorker`

What does this MR do and why?

This is one of the follow-up MRs for !106661 (merged) that to ensure the schedule_next_run! is run in either PipelineScheduleService or RunPipelineScheduleWorker to prevent it from failing the check schedule.next_run_at > Time.current at https://gitlab.com/gitlab-org/gitlab/-/blob/master/app/workers/run_pipeline_schedule_worker.rb#L23 when feature flag ci_use_run_pipeline_schedule_worker is enabled.

Otherwise, because PipelineScheduleService is used in two different places, one of them is for Play button for schedule job, the Play won't be able to run the schedule job immediately.

This is the first one to prepare RunPipelineScheduleWorker to accept next_run_scheduled option so that the fix can be completed.

Screenshots or screen recordings

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

How to set up and validate locally

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

• I have evaluated the MR acceptance checklist for this MR.

Related to #338609 (closed)