When running with --resume option the ALTER runs on the new table
even if the new table exists and has already been altered.
This causes a deterministic failure every time the --resume option
is used. This fix tests if --resume is given and does not run
ALTER on the new table. If pt-osc did not successfully alter
the new table during the previous invocation, this could cause the
ALTER to not be applied.
The right fix would be to compare the DDL of the _new table to
the proposed DDL generated by pt-osc and only run ALTER if they
do not match.
dc77289d60