fix(deps): update graalvm.version to v24.1.1

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
org.graalvm.polyglot:python (source)	24.1.0 -> 24.1.1
org.graalvm.polyglot:js (source)	24.1.0 -> 24.1.1
org.graalvm.polyglot:polyglot	24.1.0 -> 24.1.1

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[github-actions]

Hi @renovate[bot], thank you very much for your PR! ❤️
I'm a bot powered by Google AI Gemini gemini-2.0-flash-exp.
The maintainers of LangChain4j will perform a thorough code review as soon as they can, but in the meantime, here’s a preliminary review from me. I hope you find it helpful.

Potential Issues

Potential Breaking Changes

• Minor version updates in GraalVM might introduce subtle changes in behavior or performance that could affect existing applications.

Potential Design Issues

• This PR only updates the dependency version. There are no design issues introduced by this PR.

Potential Bugs

• The new GraalVM version might have introduced bugs that could affect the execution of polyglot code.

Testing

Changes in this PR are sufficiently tested: ✅

Suggested Positive Test Scenarios

• • Given: A basic code execution using Python, JavaScript, and polyglot
  • When: Running basic code execution using Python, JavaScript, and polyglot.
  • Then: The code should execute successfully with the updated GraalVM version.
• • Given: An application that uses the latest features of GraalVM
  • When: Running an application that uses the latest features of GraalVM.
  • Then: The application should function correctly and take advantage of the new features.

Suggested Negative Test Scenarios

• • Given: An application using a feature deprecated in the new GraalVM version
  • When: Running an application that relies on a deprecated feature of GraalVM.
  • Then: The application should either fail gracefully or provide a clear error message indicating the deprecated feature.
• • Given: A scenario where the new GraalVM version has a bug related to a specific language or feature
  • When: Running an application that triggers a known bug in the new GraalVM version.
  • Then: The application should either fail gracefully or exhibit the bug in a way that can be identified and addressed.

Suggested Corner Case Test Scenarios

• • Given: A GraalVM polyglot environment with specific resource constraints
  • When: Running code execution with the updated GraalVM version in a resource-constrained environment.
  • Then: The updated GraalVM version should function correctly under these constraints without unexpected errors or performance degradation.
• • Given: A complex polyglot application using multiple languages supported by GraalVM
  • When: Executing a complex polyglot application that uses Python, JavaScript, and other languages supported by GraalVM.
  • Then: The updated GraalVM version should handle the interaction between different languages without issues.

Documentation

Changes in this PR are sufficiently documented: ✅