Add Additional Geometry Types to spatial-core

As a developer using spatial-core,
I want the spatial type model to represent additional geometry types,
so that these types can be identified consistently across LongitudeOne spatial components.

Context

spatial-core provides the common representation of geometry types used by the other spatial packages.

The current model does not represent several geometry types that may be encountered by spatial formats or implementations.

These geometry types are taken from the ISO SQL/MM spatial type model defined by the normative source used by spatial-core.

The following types must be added:

• BREPSOLID
• CIRCLE
• CLOTHOID
• COMPOUNDSURFACE
• ELLIPTICALCURVE
• GEODESICSTRING
• NURBSCURVE
• SPIRALCURVE

This Story only extends the geometry type model. It does not require implementing concrete geometry classes, encoding, decoding, or format-specific support for these types.

Acceptance Criteria

• GeometryTypeEnum contains a BREPSOLID value.
• GeometryTypeEnum contains a CIRCLE value.
• GeometryTypeEnum contains a CLOTHOID value.
• GeometryTypeEnum contains a COMPOUNDSURFACE value.
• GeometryTypeEnum contains an ELLIPTICALCURVE value.
• GeometryTypeEnum contains a GEODESICSTRING value.
• GeometryTypeEnum contains a NURBSCURVE value.
• GeometryTypeEnum contains a SPIRALCURVE value.
• Each new enum value follows the naming and value conventions already used by GeometryTypeEnum.
• Existing GeometryTypeEnum values and their behavior remain unchanged.
• Tests cover all newly introduced enum values.
• The complete test suite passes without regression.

Out of Scope

• Concrete implementations of the new geometry types.
• Changes to encoder or decoder strategies.
• Format-specific serialization or parsing support.
• Changes to spatial-types.