feat: add extra property to collection and collection List

[sanzog03]

What I am changing

Add the ability to add extra parameters to collection and collectionList. Hence, they can be used to store metadata and extra information about the collection.

How I did it

In the current implementation of TiPg, a schema table in represents the whole collection and the rows represent items.
Since there is no separate table to store the collection data, If we add any columns with prefix "collection_properties_", we use that as extra properties.
A dependency injection is added which handles the above mentioned case.

How you can test it

First ingest data with a column prefixing with "collection_properties_". Then, using the API docs, test if it shows up in the collection and collection list endpoints.

[slesaad]

@vincentsarago can you please have a look at this? we're aware this isn't the best approach, but would love to hear thoughts on what that would be

[vincentsarago]

TBH I'm not sure to get the need of this. If it's to retrieve the list of properties you could use the /queryables endpoint.

This also break the OGC specification!

[bitner]

The entire goal of TiPg is to require no configuration to expose a feature service from Postgres/PostGIS tables without needing to add any additional functions/tables etc to the Postgres instance. If you require discovery of collections via metadata in the collections, I would recommend (and this is what we do at DevSeed) storing the metadata for each TiPG Collection as an Item in a Stac Catalog (ideally using PgSTAC).

[slesaad]

Hmm understood. We thought about that too, but having a collection in two different places felt redundant. But if that's what is recommended, we'll follow that.