Refactor release issue creation workflows

[gaiksaya]

Description

This change refactors release issue creation workflows to dynamically retrieve components. There was a miss in recent releases that new plugins did not receive release issues. See https://github.com/opensearch-project/opensearch-learning-to-rank-base/issues?q=is%3Aissue%20state%3Aopen%202.19.0
In order to avoid maintaining duplicate lists everywhere, example this workflow will parse the manifest files and accordingly grab all repo URLs for a given version and create issues moving forward.

Also duplicate code for issue generation now resides in create-release-issues.yml.

Issues Resolved

part of #5332

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 92.04%. Comparing base (96ab4ab) to head (822b572).
Report is 4 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #5344   +/-   ##
=======================================
  Coverage   92.04%   92.04%           
=======================================
  Files         202      202           
  Lines        7043     7043           
=======================================
  Hits         6483     6483           
  Misses        560      560           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[peterzhuamazon]

Thanks @gaiksaya !