feat(vortex-spatial): add make-line scalar function

[HarukiMoriarty]

Rationale

Vortex native geometry arrays should support constructing two-point LineStrings directly from paired Point columns without an Arrow or WKB round trip.

What changes are included?

• Add vortex.st.make_line for paired native Point arrays.
• Promote mixed XY, XYZ, XYM, and XYZM inputs, filling absent ordinates with zero.
• Propagate CRS metadata, constants, and endpoint nulls.
• Build native LineString storage directly and add focused tests and CodSpeed benchmarks.

Stack

Depends on #9291 for primitive Interleave execution. That general vortex-array capability is reviewed separately from the spatial function.

ST_Length was split into #9290 so each scalar function can also be reviewed independently.

[codspeed-hq]

Merging this PR will not alter performance

✅ 259 untouched benchmarks
⏩ 1763 skipped benchmarks¹

---

_{Comparing nemo/geo-native-bbox-precheck (1698f91) with nemo/interleave-primitive-execution (0b5c2ac)²}

Footnotes

1. 1763 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩

2. No successful run was found on nemo/interleave-primitive-execution (6ad96f8) during the generation of this report, so 9f4aa0e was used instead as the comparison base. There might be some changes unrelated to this pull request in this report. ↩

[connortsui20]

@claude review this PR, and look for potential regressions as well as inconsistencies with other code that is not in this PR

[github-actions]

Claude encountered an error after 2s —— View job

---

I'll analyze this and get back to you.

[github-actions]

Claude encountered an error after 2s —— View job

---

I'll analyze this and get back to you.

[connortsui20]

discussed offline, should pull out the interleave perf optimizations out of this PR

[connortsui20]

in what cases do you ever run into an "absent ordinate", and is returning 0.0 really ok here? instead of null, for example?

its a bit hard for me to understand why we want this behavior in the create linestring functionality

[HarukiMoriarty]

“absent ordinate” only occurs with mixed-dimensional inputs. We promote the output dimension to the union of both inputs and fill missing Z/M values with zero, matching DuckDB’s ST_MakeLine behavior.

Null would represent a null coordinate inside an otherwise valid geometry and is not supported by the native LineString coordinate storage.

[HarukiMoriarty]

e.g. XYZ + XYM → LINESTRING ZM (..., 2 2 0 3) https://github.com/duckdb/duckdb-spatial/blob/c27bc2b0091f75e97c189d345f37a3771dfef89c/test/sql/geometry/st_makeline.test

[connortsui20]

Ok LGTM, but please pull out the interleave optimizations before you merge