Feature/api features

[herzogrh]

This pull request introduces support for associating OGC API endpoints with model versions, enabling more flexible integration with geospatial data sources. The changes include database schema updates, backend logic for serialization/deserialization of OGC endpoint data, enhancements to the simulation adapter for dynamic endpoint handling, and updates to the frontend form for improved endpoint selection.

OGC Endpoint Integration

• Added a new ogcEndpoints JSONB column to the models_versions table, seeded with the Hamburg API as the default endpoint for all existing model versions.
• Updated the backend schema (models-versions.schema.ts) to define and include the ogcEndpoints field in model version data structures and validation. [1] [2] [3]
• Implemented hooks in the backend service (models-versions.ts) to handle proper serialization and deserialization of the ogcEndpoints field for create, patch, and response operations. [1] [2] [3]
• Ensured that new model versions are initialized with an empty ogcEndpoints array and that the field is always a valid JSON array when creating drafts. [1] [2]

Simulation Adapter & Node Schema Enhancements

• Extended the node schema to support endpoint-specific fields (endpointId, baseUrl, apiType) for OGC feature nodes, allowing nodes to reference specific endpoints and API types.
• Refactored the OGC API features client and simulation primitive factory to dynamically use the endpoint's base URL and handle single/multi-API endpoints, including improved error handling and logging. [1] [2] [3] [4]

Frontend Improvements

• Updated the node form fields to allow users to select an OGC endpoint and, for multi-API endpoints, choose a specific API, improving the user experience for configuring OGC feature nodes.

Version Bump

• Incremented the backend package version to 1.0.0-12 to reflect these new capabilities. [1] [2]