chore: Upgrade org.locationtech.jts version to 1.20.0

[sumi-mathew]

Description

Upgrade org.locationtech.jts version to 1.20.0

Motivation and Context

Using a more recent version helps avoid potential vulnerabilities and ensures we aren't relying on outdated or unsupported code.

Impact

Test Plan

Contributor checklist

• Please make sure your submission complies with our contributing guide, in particular code style and commit standards.
• PR description addresses the issue accurately and concisely. If the change is non-trivial, a GitHub Issue is referenced.
• Documented new properties (with its default value), SQL syntax, functions, or other functionality.
• If release notes are required, they follow the release notes guidelines.
• Adequate tests were added if applicable.
• CI passed.
• If adding new dependencies, verified they have an OpenSSF Scorecard score of 5.0 or higher (or obtained explicit TSC approval for lower scores).

== NO RELEASE NOTE ==

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Upgrades the org.locationtech.jts dependency to 1.20.0 and aligns geospatial geometry validation tests with updated JTS error messages.

File-Level Changes

Change	Details	Files
Bump JTS library version used by the project.	Update the shared Maven property controlling org.locationtech.jts version from 1.19.0 to 1.20.0 Ensure dependent modules will resolve and build against JTS 1.20.0 without further code changes	pom.xml
Adjust geospatial invalid-geometry tests to match new JTS validation error text.	Update expected invalid reason string for a self-intersecting polygon from "Ring Self-intersection" to "Self-intersection" in polygon-only case Update expected invalid reason string for a self-intersecting polygon inside a geometry collection from "Ring Self-intersection" to "Self-intersection"	presto-main-base/src/test/java/com/facebook/presto/geospatial/TestGeoFunctions.java

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey - I've left some high level feedback:

• The tests that assert exact JTS error strings (e.g., "Ring Self-intersection" vs "Self-intersection") are tightly coupled to the library’s internal messages; consider relaxing these to check for a stable substring or error type so future JTS updates don’t require test rewrites for wording changes.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- The tests that assert exact JTS error strings (e.g., "Ring Self-intersection" vs "Self-intersection") are tightly coupled to the library’s internal messages; consider relaxing these to check for a stable substring or error type so future JTS updates don’t require test rewrites for wording changes.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[agrawalreetika]

Lgtm, just have one question

[agrawalreetika]

Do we know what changed in tests after upgrade?

[sumi-mathew]

Before (1.19.0): "Ring Self-intersection" - Used for all polygon ring self-intersections
After (1.20.0): "Self-intersection" - Used for certain types of polygon self-intersections
Still Returns "Ring Self-intersection": Complex ring intersections involving multiple segments

[hantangwangd]

Thanks @sumi-mathew