[Bug]: The [AUTOCUT] issues does not have the updated information and close once the issue is resolved

[prudhvigodithi]

Describe the bug

The existing [AUTOCUT] issues for integ-test failures (Example opensearch-project/security#3011) and distribution build failures (Example opensearch-project/k-NN#957) does have the latest information, this is because the existing logic looks for an issue created and simply skips. This is a problem as the latest build information is not updated to the issue body.

This is causing a huge problem for an release-manager to always gather the latest logs and post as a comment or as a hack close the issue created (example opensearch-project/k-NN#957) and allow the logic to re-create again (example opensearch-project/k-NN#975). This not only required a manual task for an release-manager to close the issue, but also cause to create multiple issues in the repo and this keeps growing for the same version if we close and allow to re-create again.

The Second part is the [AUTOCUT] once created they never gets closed until an release-manager or a repo owner identifies and close the issue.

To reproduce

The existing logic, a sample build https://build.ci.opensearch.org/job/distribution-build-opensearch/8194/consoleText

+ gh issue list --repo https://github.com/opensearch-project/reporting.git -S '[AUTOCUT] Distribution Build Failed for opensearch-reports-3.0.0 in:title' --label autocut,v3.0.0
[Pipeline] echo
Issue already exists in the repository, skipping.

The existing AUTOCUT issue points to build number 8083, but the latest failed build (as of this issue creation) is 8194

Expected behavior

The expected behaviour is, instead of just skipping the issue creation, if the issue exists add a new comment with the latest failed build.

This will solve from closing the existing issue and adding the latest failed build information.

Screenshots

If applicable, add screenshots to help explain your problem.

Host / Environment

No response

Additional context

No response

Relevant log output

No response

[prudhvigodithi]

Adding comment with latest build fail information: opensearch-project/job-scheduler#433 (comment) (The comments keeps increasing when the build frequency is more, I’m open for ideas to fine tune this behaviour)
Close the issue when component passed: opensearch-project/common-utils#430 (comment)
Build log: https://build.ci.opensearch.org/job/distribution-build-opensearch/8206/console