Enhance changelog verifier script

[kotwanikunal]

Description

• This change will work in tandem with Create separate file for unreleased 3.0 changes #13040
• The workflow ensures that an entry exists in either CHANGELOG-2.0 or CHANGELOG-3.0 and fails if it does not exist in either
• Also reduces the number of instantiations by reducing the event triggers
• Test PR: Test PR kotwanikunal/OpenSearch#159

Related Issues

Resolves #13013

Check List

• New functionality includes testing.
  • All tests pass
• New functionality has been documented.
  • New functionality has javadoc added
• Failing checks are inspected and point to the corresponding known issue(s) (See: Troubleshooting Failing Builds)
• Commits are signed per the DCO using --signoff
• Commit changes are listed out in CHANGELOG.md file (See: Changelog)
• Public documentation issue/PR created

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.

[reta]

@kotwanikunal curious if we should be using CHANGELOG-3.x.md since it will be moving target essentially (like CHANGELOG-2.x.md which would correspond to 2.14.0 as of today)

[kotwanikunal]

Sounds like a discussion for the other PR. Let me move this commit onto that branch and we can finalize the file names/convention on that thread.

[github-actions]

Compatibility status:

Checks if related components are compatible with change b4413e0

Incompatible components

Skipped components

Compatible components

Compatible components: [https://github.com/opensearch-project/custom-codecs.git, https://github.com/opensearch-project/asynchronous-search.git, https://github.com/opensearch-project/performance-analyzer-rca.git, https://github.com/opensearch-project/cross-cluster-replication.git, https://github.com/opensearch-project/job-scheduler.git, https://github.com/opensearch-project/reporting.git, https://github.com/opensearch-project/security.git, https://github.com/opensearch-project/geospatial.git, https://github.com/opensearch-project/flow-framework.git, https://github.com/opensearch-project/common-utils.git, https://github.com/opensearch-project/k-nn.git, https://github.com/opensearch-project/opensearch-oci-object-storage.git, https://github.com/opensearch-project/neural-search.git, https://github.com/opensearch-project/anomaly-detection.git, https://github.com/opensearch-project/performance-analyzer.git, https://github.com/opensearch-project/security-analytics.git, https://github.com/opensearch-project/ml-commons.git, https://github.com/opensearch-project/notifications.git, https://github.com/opensearch-project/observability.git, https://github.com/opensearch-project/index-management.git, https://github.com/opensearch-project/alerting.git, https://github.com/opensearch-project/sql.git]

[github-actions]

❌ Gradle check result for b4413e0: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[github-actions]

❌ Gradle check result for e086d1b: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[andrross]

Great work @kotwanikunal! Let's work through the discussion on #13040 and then maybe fold this commit into the PR directly since this is a small change tightly coupled to that PR?

[dbwiddis]

LGTM and thank you!

[kotwanikunal]

Great work @kotwanikunal! Let's work through the discussion on #13040 and then maybe fold this commit into the PR directly since this is a small change tightly coupled to that PR?

Sure. I'll cherry-pick this commit onto your branch.

[kotwanikunal]

Changes moved to #13040