This fixes an issue experienced during pypgstac migrate,
which causes failures due to the version being
returned is "bytes" and not a string.

* Point commit for hydration work.

Trying to get pip installable

* pip installable with setup.py

* Get tests running with new configuration

* Dehydration checkpoint

* Hydrate accounts for do-not-merge marker

* Remove incorrect copy values

* Remove extra print

* Alternate package install technique

Fixing CI issues

* Install psycopg as an extra

* Publish with twine

* Remove poetry lock update script

* Remove poetry from staging process

Requires that the user explicitly state the updated version.

* Require local install of pypgstac.

This is required because the dev docker-compose mounts the entire source
tree into the container. This overwrites the local python egg
for the package, and causes failures.

* Run install on cibuild

Co-authored-by: Rob Emanuele <rdemanuele@gmail.com>

* Include pgstac migrations in pypgstac package

* Add tests for specific invalid asset regression

We've had both db and api regressions where assets would be included in
the hydrated item without an href causing validation errors. Adding
specific tests for this case to make sure the general do-no-merge key
solution address this problem, and the api-fix can be removed from
stac-fastapi backend.

* Clarify comments and variable names

* On the recursive portion of the dehydrate function, base_item and
full_item are not actual items, but sub-keys from root. Move to a
private inner function with clearer names, similar to hydrate.
* Update comments to be more precise with respect to leaving items on
the item or not.

* Set autocommit on new connections.

See https://www.psycopg.org/psycopg3/docs/basic/transactions.html?msclkid=496fe3b1d0d511eca8f7aae193c127a1#transaction-contexts

* Use package-specific logger

* Formatting.

* Remove Stable declaration from delete_items function

* Python dehydrate marks top-level base_keys as DNM

Fixes and tests that dehydration is aware of top-level keys on the base
item which should be marked as do-not-merge on the dehydrated item.

* Fix test class to use hydration module

* update changelog


* update tests for changes in fields extension, add simpler testing for sql queries

* update version to 0.6.0, update changelog

* add triggers to allow deleting collections and cleaning up partitions

Co-authored-by: Rob Emanuele <rdemanuele@gmail.com>
Co-authored-by: Matt McFarland <mmcfarland@microsoft.com>