Successful rollbacks should remove or invalidate deployments from the tracking DB

[nativestranger]

No description provided.

[cjestel]

We'll see if we can get to this one. JP and I talked about making updates like this off hours while we are at pgwest in another week or two. This feature was intentionally left out when built because from a prod perspective we don't ever rollback a migration, we would copy the rollback to the changes folder and deploy as a new migration so that the timeline of production isn't capable of being off from what may be deployed to test (aka, prod having moved forward and then back while test env's just moved forward).

We've discussed making this a config option so that in test env's a rollback is officially supported. We also have discussed a --rollback X option where X is an integer to specify the number of migrations to rollback without having to pass in file names