Provide a cleanup mechanism for cases when source (or destination) no longer exists (DropMirror)

[iamKunalGupta]

During DropFlow, if the source PG does not exists, we run into infinite retries with failed to get source connector: failed to create connection: failed to connect to user=postgres database=postgres:\n\thostname resolving error: lookup db.fsujzxgaybt

Can we (maybe) implement a signal to bypass this activity manually if needed? No need to automate the DropFlow itself

[heavycrystal]

the retries shouldn't be infinite, the DropFlow cancels after a few minutes

[serprex]

this now resolves on its own after ~12 hours