Update unsupported spatial types for spatial-core 1.3

As a developer using spatial-types,
I want the library to support the geometry type definitions introduced by spatial-core 1.3,
so that every instantiable geometry type exposed by spatial-core has an explicit implementation status.

Context

This Story requires spatial-core 1.3.0, which introduces the additional geometry types listed below in GeometryTypeEnum.

These types are part of the spatial model but are not yet implemented by spatial-types. They must therefore be explicitly classified as not yet implemented by SpatialTypeImplementationStatus.

The minimum required version of longitude-one/spatial-core must also be updated from ^1.2 to ^1.3.

The new geometry types are:

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

Acceptance Criteria

• The longitude-one/spatial-core Composer dependency is updated from ^1.2 to ^1.3.
• SpatialTypeImplementationStatus explicitly handles every new instantiable geometry type introduced by spatial-core 1.3.0.
• BREPSOLID is classified as not yet implemented.
• CIRCLE is classified as not yet implemented.
• CLOTHOID is classified as not yet implemented.
• COMPOUNDSURFACE is classified as not yet implemented.
• ELLIPTICALCURVE is classified as not yet implemented.
• GEODESICSTRING is classified as not yet implemented.
• NURBSCURVE is classified as not yet implemented.
• SPIRALCURVE is classified as not yet implemented.
• SpatialTypeImplementationStatus::isFullyImplemented() returns false for each of these new types.
• The exhaustive GeometryTypeEnum coverage test is updated with the new enum cases.
• Tests verify the implementation status of the newly introduced types.
• No instantiable GeometryTypeEnum case results in an undefined implementation status.
• Existing implementation statuses remain unchanged.
• The complete test suite passes.
• Project quality checks pass.