[Bug]: Build Failure issues often open/close within minutes

[gaiksaya]

Describe the bug

Autocut build failure issues creating as an action item for component teams do not honor the platform, architecture, etc. The current logic blinding parses the error messages and closes/re-opens the issues.
See: https://github.com/issues?q=is%3Aopen+is%3Aissue+archived%3Afalse+user%3Aopensearch-project+label%3Aautocut+%22%5BAUTOCUT%5D+Distribution+Build+Failed+for+%22

To reproduce

Observe the log messages in distribution pipeline

Expected behavior

Only close the issue if there is no recent failure on any stages.

Screenshots

Acceptance Criterias

• Only close the issue if there is no recent failure on any stages

[gaiksaya]

Had a discussion with @prudhvigodithi
This is caused because both libraries are called one after the other here: https://github.com/opensearch-project/opensearch-build/blob/main/jenkins/opensearch/distribution-build.jenkinsfile#L782-L792

One way to fix this is compare the passing components with the failed ones and only close the delta.

Passing components ArrrayList: https://github.com/opensearch-project/opensearch-build-libraries/blob/main/vars/closeBuildSuccessGithubIssue.groovy#L19
Failing components ArrayList: https://github.com/opensearch-project/opensearch-build-libraries/blob/main/vars/createBuildFailureGithubIssue.groovy#L28