Pass exact through point intersections

[Maximus-08]

Summary

• expose the exact keyword on public intersection_points entrypoints
• pass exact through intersection(...; target = GI.PointTrait()) to _intersection_points
• add regression tests for both public point-intersection paths with exact = false

Before this change:

• _intersection_points(...; exact=...) already supported the keyword
• intersection_points(...) dropped it
• intersection(...; target = GI.PointTrait()) also dropped it

That meant users could not control the exact/inexact predicate path from the supported public APIs.

Testing

• full package test suite passed

Documenter errors like CurrentModule = GeometryOpsCore failing because GeometryOpsCore was not defined in Main during doctest evaluation. This error is also seen in the CI doctest

[Copilot]

Pull request overview

This PR makes the exact predicate-mode keyword controllable from the supported public point-intersection APIs, so callers can explicitly choose the exact vs inexact predicate path rather than being forced into the default.

Changes:

• Exposes exact on intersection_points(...) entrypoints and forwards it down to _intersection_points.
• Adds exact to intersection(...; target = GI.PointTrait()) by passing it through to the point-intersection implementation.
• Adds regression tests covering both public point-intersection paths with exact = false.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File	Description
src/methods/clipping/intersection.jl	Threads exact through intersection (PointTrait target) and intersection_points to _intersection_points, and updates intersection_points docs.
test/methods/clipping/intersection_points.jl	Adds regression tests ensuring exact = false works via both intersection_points and intersection(...; target=PointTrait()).

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.