Implement faster ST_Boundary() using `geo-traits`

Thank you! (Especially for the geometrycollection investigation and implementation!)

I'll open a follow-on ticket for whenever any of us has time...this is an example of a function that is a good candidate for implementing with geo-traits directly for performance reasons.

_Originally posted by @paleolimbot in https://github.com/apache/sedona-db/pull/298#pullrequestreview-3462374262_

The issue names ST_Boundary() and geo-traits but does not identify files or tests. Start by locating the ST_Boundary() implementation and its existing geometry handling, then identify the relevant performance test or benchmark; done means a geo-traits-based implementation with validated faster behavior.

Written by the indexing model from the issue text.