Force snakeyaml_engine version

[reta]

Description

Fixes

[0](https://github.com/opensearch-project/sql/actions/runs/34537191302/job/103071491521#step:6:391)
   > Could not resolve org.snakeyaml:snakeyaml-engine:3.1.1.
You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.
     Required by:
         project ':opensearch-sql-plugin' > project :ppl > project :core
         project ':opensearch-sql-plugin' > org.opensearch:opensearch:3.9.0-SNAPSHOT:20260910.203459-124 > org.opensearch:opensearch-x-content:3.9.0-SNAPSHOT:20260910.203459-124
      > Conflict found for module 'org.snakeyaml:snakeyaml-engine': between versions 3.1.1 and 3.0.1
> There is 1 more failure with an identical cause.

Related Issues

See please https://build.ci.opensearch.org/job/distribution-build-opensearch/12192

Check List

• New functionality includes testing.
• New functionality has been documented.
• New functionality has javadoc added.
• New functionality has a user manual doc added.
• New PPL command checklist all confirmed.
• API changes companion pull request created.
• Commits are signed per the DCO using --signoff or -s.
• 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]

@gaiksaya @peterzhuamazon fyi

[github-actions]

PR Code Analyzer ❗

AI-powered 'Code-Diff-Analyzer' found issues on commit 76afa85.

Path	Line	Severity	Description
build.gradle	168	high	New dependency added: 'org.snakeyaml:snakeyaml-engine' under a different group ID ('org.snakeyaml') than the existing snakeyaml dependency ('org.yaml:snakeyaml'). The version is sourced from an external versions variable (${versions.snakeyaml_engine}) whose definition is not visible in this diff. Per mandatory supply chain policy, all dependency additions must be flagged regardless of apparent legitimacy. Maintainers should verify the artifact origin, confirm the group ID is the canonical publisher, and audit the resolved version value.

The table above displays the top 10 most important findings.

Total: 1 | Critical: 0 | High: 1 | Medium: 0 | Low: 0

---

Pull Requests Author(s): Please update your Pull Request according to the report above.

Repository Maintainer(s): You can bypass diff analyzer by adding label skip-diff-analyzer after reviewing the changes carefully, then re-run failed actions. To re-enable the analyzer, remove the label, then re-run all actions.

---

⚠️ Note: The Code-Diff-Analyzer helps protect against potentially harmful code patterns. Please ensure you have thoroughly reviewed the changes beforehand.

Thanks.