feat(bindings): temporal similarity measures (Frechet, DTW, Hausdorff)

[estebanzimanyi]

Summary

Adds 8 ScalarFunction registrations for temporal similarity measures:

Function	MEOS
frechetDistance(t1, t2)	temporal_frechet_distance
discreteFrechet(t1, t2)	temporal_frechet_distance (alias)
dynTimeWarp(t1, t2)	temporal_dyntimewarp_distance
hausdorffDistance(t1, t2)	temporal_hausdorff_distance

For each: (tint, tint) and (tfloat, tfloat) registrations.

Implementation uses 3 thin wrappers + a single TempTempDoublePred templated helper.

similarityPath (table-returning, alignment) is intentionally NOT included — needs DuckDB TableFunction infrastructure (separate follow-up tracked in PR #23).

Smoke test

SELECT frechetDistance(tfloat '[1@01-01, 2@01-02]', tfloat '[2@01-01, 3@01-02]');   -- 1.0
SELECT discreteFrechet(tfloat '[1@01-01, 2@01-02]', tfloat '[2@01-01, 3@01-02]');   -- 1.0
SELECT dynTimeWarp(tfloat '[1@01-01, 2@01-02]', tfloat '[2@01-01, 3@01-02]');       -- 2.0
SELECT hausdorffDistance(tfloat '[1@01-01, 5@01-05]', tfloat '[3@01-01, 3@01-05]'); -- 2.0

Test plan

• make release then TZ=UTC ./build/release/test/unittest "<proj>/test/*" — full suite passes.
• After merge, PR test(parity): batch port — tile / math / distance / similarity (4 manifest files) #23's 038_temporal_similarity.test skip block partially unwraps (the scalar measures activate; similarityPath stays gated on TableFunction infra).

Dependencies

Stacked on PR #35 (ever/always ordering). Merge order: #27 → #29 → #30 → #31 → #32 → #33 → #34 → #35 → this.

[estebanzimanyi]

@nhungoc1508 — heads up: this PR is marked merged but its content did not reach main. PR #36's base was feat/temporal-everalways-comparisons (PR #41's branch). The squash-merge added the squashed commit 2cc6373 to feat/temporal-everalways-comparisons rather than to main.

PR #41's branch now carries this commit. When PR #41 lands in main, its squash-merge will combine PR #41's own content with PR #36's content into a single commit. The functional code reaches main, but PR #36 will not appear as its own merge commit in main's history.

If you want a clean attribution: I can re-PR PR #36's content as a separate PR rooted on main, after PR #41 lands. Otherwise it's fine to let the combined squash carry both.