Add the Multi-Tenant Catalogs Endpoint Extension, for nested catalog support

[jonhealy1]

Related Issue(s):

• Implementing the Multi-Tenant Virtual Catalogs STAC API Extension #376
• Nested catalogs in stac-fastapi-pgstac #79
• Multi-tenant /Catalogs Extension stac-fastapi#880
• Hierarchically organized STAC APIs pgstac#88

Description:

Extension spec: https://github.com/StacLabs/multi-tenant-catalogs
STAC-FastAPI catalogs extension: https://github.com/StacLabs/stac-fastapi-catalogs-extension

PR Checklist:

• pre-commit hooks pass locally
• Tests pass (run make test)
• Documentation has been updated to reflect changes, if applicable, and docs build successfully (run make docs)
• Changes are added to the CHANGELOG.

[jonhealy1]

It's going to be best to fix the extension so it supports python 3.11

[jonhealy1]

This is really close to being reviewable, just need some time to do some qa, documentation.

[jonhealy1]

When parent_ids are added to a collection, all parent_ids are present, not just parents in the current catalog "tree".

For example:

@bkanuka There is a glitch here, that needs to be fixed. The parent_ids list should not be returned to the client via an API response. The parent_ids list should only be present in Postgres.

[jonhealy1]

@bkanuka Thanks for the feedback. I have implemented the two suggestions you made. Removing parent_ids from collection responses and fixing/ improving the self link generation.

[jonhealy1]

@vincentsarago Thanks for reviewing. I have implemented most of your suggestions - except for the name change.

I have also updated the catalogs extension to v0.2.0 which basically just means a separate catalogs transactions class. My thinking is that the catalogs transaction routes will only be implemented when the core transaction extension is enabled. This may be too simplistic, let me know what you think.

Additionally I added some documentation to the readme and settings.md.