Incorrect offset may be committed despite unparseable DDL statements

If there's an unparseable DDL statement and the schema changes topic is enabled, it may happen that the offset of that DDL event gets committed by Kafka Connect (the reason being that poll() may emit the corresponding SourceRecord before the failure property is set which will stop the connector eventually. This should not happen, i.e. such unparseable DDL event should not be propagated.