Full Teardown fails - "user not permitted to log in"

[vjeeva]

Describe the bug
The teardown --full function fails to run to completion because the command tries to run things on the source database with a user that has LOGIN revoked. This occurs after pgbelt is used for a migration, so users on the source DB have login revoked.

To Reproduce
Steps to reproduce the behavior:

1. Run a pgbelt migration with a cutover (using revoke-logins to ensure traffic has stopped on the source database)
2. After the migration is complete, run teardown --full.

Expected behavior
Must fully tear down replication, the extension, deleting the pglogical user, etc.

[vjeeva]

The issue is here: https://github.com/Autodesk/pgbelt/blob/main/pgbelt/cmd/teardown.py#L90-L91

Those revokes need to be run by the schema owners of both databases (which have their logins revoked).

ALTERs are idempotent so we could ALTER WITH LOGIN before those lines. Removing login again after those lines should depend on in revoke-logins was run in the first place.

Maybe we can just ALTER WITH LOGIN for now, no need to really revoke that later anyways since teardown would occur well after the migration is complete.

[vjeeva]

Wow I forgot we wrote a restore-logins command. We should run that before teardown --full and should be fine.

[vjeeva]

We can run the REVOKEs as admin, solves the issue much easier.