Deploying and rolling back changes in an Availability Group database
There's not really a practical method. I can really think of three ways of rolling back a failed deployment:


BEGIN \ ROLLBACK TRANSACTION: Normally, this is what I'd recommend - it's cleanest, and you wouldn't have to suspend data movement to do it. However, since you need to be able to view the changes from another machine, it's not really an option.
Rollback script: With this, you pre-script the commands required to return the database to the state it was in prior to the deployment. It's not a true rollback, and it may be impractical on a large database in some circumstances.
RESTORE DATABASE: As you mentioned, there are hassles for this on a large database in an AG.