Patch release job for verifying for projects under managed versioning

What does this MR do and why?

This is follow up to !3508 (merged), to actually call ManagedVersioningNotificationService in the patch release pipeline.

Also updated the patch release task template.

Addresses: gitlab-com/gl-infra/delivery#20229 (closed)

Testing

Creation

With SECURITY_RELEASE_PIPELINE=true	With SECURITY_RELEASE_PIPELINE='disable_issue_processor'
it's run after security_release_disable_issue_processor_schedule:start is completed:
Pipeline	Pipeline

Config and execution

Testing the execution order of the jobs. I commented out the previous job, and return an empty array for pending issues (commit)

Step	Screenshot
Initialized as manual pipeline (Pipeline) SLACK_TEST = true TEST = true SECURITY_RELEASE_PIPELINE = disable_issue_processor
After the security_release_disable_issue_processor_schedule:start job is triggered, the security_release_disable_issue_processor_schedule:verify-managed-version-projects job starts.
The pipeline successfully finishes as there are no issues under managed versioning. The slack message would normally send, but this pipeline was run as dry mode (TEST)
Here is an example of the job encountering issues under managed versioning, and outputting a list of issues as expected.