Monthly release: check omnibus packages after tagging

What does this MR do and why?

Describe in detail what your merge request does and why.

Content

• Monthly release: check omnibus packages after tagging

Automate the step of checking Omnibus packages after tagging. Because the tagging step is still manual, this check still needs to be triggered manually.

Testing

Pipeline creation

This was tested in this repo (gitlab-org/release-tools), just to see that the pipeline gets created as we expect it.

With MONTHLY_RELEASE_PIPELINE=true	With MONTHLY_RELEASE_PIPELINE='tag_day'
The new job monthly_release_tag_day:check_omnibus_packages_tagging is a part of the stage monthly_release:tag_day . As you can see, the new job needs a manual trigger.
Pipeline	Pipeline

Configuration testing

This is a manual task, so we don't need to test the job order.

Execution testing

Since this task only performs checking, it is safe to test without any code change.

Step	Screenshot/link
Initialized as manual pipeline (Pipeline) SLACK_TEST = true MONTHLY_RELEASE_PIPELINE = tag_day The start job finished and started the other 2 jobs of the tag_day stage automatically (I had to stop them manually)	(Please ignore the allow_failure of the job. It was a bug and I fixed it in the latest version)
Slack notification when the job starts (link)
When triggering the job manually, it runs but fails because we are not at the tagging time yet (job)	2024-09-05 10:11:20.471103 F Rake::Task -- Task failed -- Exception: ReleaseTools::Services::OmnibusPackages::Base::OmnibusPackagesError: No Omnibus packages found for 17.4.0
A slack notification is posted (link)
If I manually set version to 17.3.0, the job succeeded and posted a Slack message (FYI, in 17.3.0, the bridge job's name had a typo check-package-functionality (instead of "packages"))