Migrate all constraint names

We need to migrate the names of constraints properly. This needs to be done in the finalization.
The names are defined within our schema. It gets lost during table copy during the migrate step. The solution would possibly entail reimplementing the postgres naming convention and renaming the constraints in our naming convention.

Here is an example snippet to check correct the behaviour of migration 100 in the case of primary keys. You can add it to the check_data method.

                # 6.9 Recreated primary key constraints
                assert_content_not_none(
                    """SELECT 1
                    FROM information_schema.table_constraints AS tc
                    WHERE tc.constraint_type = 'PRIMARY KEY'
                        AND tc.constraint_name = 'pk_nm_chat_group_read_group_ids_group_t';"""
                )

An extension for what is being done for the foreign keys could be sufficient. (migration handler line 85)

NOT NULL, DEFAULT and GENERATED ALWAYS constraints are not named by postgres. Thus these could be taken off their names if we don't find a reason why we want to find these names in the sql file. It wouldn't need a migration for these as they are already omitted by postgres.

Start with the migration handler around line 85 and the table-copy step in migrate, then inspect how schema constraint names reach finalization. Add the primary-key case to migration 100's check_data method using the information_schema query shown. Done means named primary-key and foreign-key constraints survive migration with the project's naming convention, while unnamed PostgreSQL constraints remain appropriately handled.