Fix collection extent

[anayeaye]

What

Use inbuilt pgstac utility function pgstac.collection_extent(collection_id text) to apply the maximum date range from the items partitions instead of the outdated collection_temporal_extent utility that uses only the nominal item datetime.

How tested

I executed and verified this method in a test database deployed for this backend pr. I'm still trying to think of ways to test the actual changes in the ingestor but the updating dev deployment and running an actual ingest may be the easiest way to go.

UPDATE collections set content = content || pgstac.collection_extent(collections.id)
WHERE collections.id = :_collection;

NASA-IMPACT/veda-backend#211

[ividito]

Would the same thing be accomplished by toggling the update_collection_extent setting in pgstac? This is currently set to false in our dev environment. The code looks similar, but I'm not certain what the practical difference is.

[anayeaye]

accomplished by toggling the update_collection_extent setting in pgstac

@ividito yes! that's the ultimate plan but we will need to set up pg_cron to schedule the event. That's next in line after testing and pushing the changes to GHGC. For now this is a quick fix we want to test in an easier VEDA environment before GHGC which is heading to production very soon.

[slesaad]

LGTM