Build the pinned MEOS with the CBUFFER, NPOINT, POSE and RGEO modules

[estebanzimanyi]

The MobilityDuck extended temporal type ports (tcbuffer, tnpoint, tpose, trgeometry) cannot link until the vcpkg-built MEOS exposes those modules. MEOS builds them opt-in and RGEO is a dependent option that requires POSE, so all four are enabled together in the vcpkg portfile OPTIONS, leaving each subsequent type port as pure extension code. Stacked on #134 because main's pinned MEOS predates the symbols these modules need and #134 already advances the pin; #134's pin-bump commit shows in the diff until it merges. The OPTIONS edit is independent of the REPO/REF/SHA512 pin lines that #142 and #143 rewrite, so it composes with whichever pin lands and needs only ordering, not textual reconciliation, against those PRs.

[estebanzimanyi]

Reviewer's quickstart — ~2 minutes

What this PR does in one sentence: flips the MEOS build flags in vcpkg_ports/meos/portfile.cmake to compile the CBUFFER, NPOINT, POSE, and RGEO extension-type modules into the pinned MEOS.

Files (1): vcpkg_ports/meos/portfile.cmake — single-file change adding -DMEOS_CBUFFER=ON -DMEOS_NPOINT=ON -DMEOS_POSE=ON -DMEOS_RGEO=ON (or equivalent) to the vcpkg CMake invocation.

Unlocks: the feat/*_port_core stack (#148/#150/#151/#153/#155/#156) — each of those PRs registers DuckDB UDFs that need the corresponding MEOS-side modules linked.

Cross-link: stacked on #134 (the base pin bump). Once #134 lands, this rebases on main and the *_port_core PRs can adopt this MEOS.

Why it's safe to merge: pure build-flag change; doesn't alter source code.