feat: update versions for pgstac, stac-fastapi-pgstac, titiler-pgstac, and tipg

[hrodmn]

⚠️ Checklist if your PR is changing anything else than documentation

• Posted the link to a successful manually triggered deployment workflow (successful including the resources destruction) https://github.com/developmentseed/eoapi-cdk/actions/runs/13770174796

I also manually created a deployment with integration_tests/cdk/app.py and verified that all of the services are working with these changes.

Merge request description

Update versions for the core dependencies! Should this be a major version change since there are breaking changes in the APIs for stac-fastapi-pgstac (stac-fastapi>=0.5) and titiler-pgstac (from titiler>=0.19)?

Resolves #115

I don't love using os.environ.update(...) to set the postgres settings in the handlers, but that is the only way to load e.g. stac_fastapi.pgstac.app since that module will load settings from the environment and fail if the POSTGRES_* variables are not set in the environment. We can load these settings in the new config modules, but to use the custom settings we have to completely re-define the app module in this repo - I would much rather use the pre-defined app variables here to make long-term maintenance easier.

@vincentsarago what do you think? We could refactor titiler-pgstac and stac-fastapi-pgstac a little bit so the application modules can be loaded even if those environment variables are present, then fail loudly on application startup if they are not configured.

One option would be to update the Lambda constructs with those POSTGRES_* environment variables set directly rather than setting PGSTAC_SECRET_ARN. I know we used to do that in eoapi-devseed but maybe it's not ideal from a security standpoint.

[hrodmn]

I opted to remove all of the custom app and config modules in favor of the default applications that get shipped with stac_fastapi.pgstac and titiler.pgstac. This simplifies the process of updating default versions in eoapi-cdk in the future and hopefully reduce confusion for users. You either get the default application that is shipped with titiler.pgstac==x.x.x or you can write a custom runtime.

[hrodmn]

I have deployed a less temporary stack with these changes:
stac-fastapi-pgstac: https://mc8hmu6918.execute-api.us-east-1.amazonaws.com/
tipg: https://jnghrxspsi.execute-api.us-east-1.amazonaws.com/
titiler-pgstac: https://dg7bp9uptd.execute-api.us-east-1.amazonaws.com/

Everything seems to be working well with the default applications that are shipped with the tipg/titiler-pgstac/stac-fastapi-pgstac packages. Do these changes warrant a major version release? I think we might be due for v8.0 because of the breaking API changes that we are adding in the default titiler-pgstac and stac-fastapi-pgstac runtimes.

I will see about updating the documentation to help users understand the default behavior and point towards examples of how to customize the applications.

[vincentsarago]

Do these changes warrant a major version release? I think we might be due for v8.0

👍