Rollback to savepoint is ignored for mixed transactions [DBZ-533]

Migrated from [DBZ-533](https://issues.redhat.com/browse/DBZ-533)

When a transaction contains a temporary tbale operation and savepoint and rollback to savepoint is used then binlog contains both {{SET SAVEPOINT}} and {{ROLLBACK TO}} statements together with statements that should be rolled out.

No files, tests, or entry points are identified. Start by reproducing a mixed transaction containing a temporary table operation, a savepoint, and a rollback to that savepoint, then inspect the resulting binlog. Done means the binlog no longer includes statements that should have been rolled back.

Written by the indexing model from the issue text.