Which use case/requirement will be addressed by the proposed feature?

We often face an issue when MySQL source connector "loses" GTID. It may be caused by GTID purging configuration on MySQL side that our team can not change.

Also there is some GTID related bugs (DBZ-8194)

On the other hand when GTIDs are purhed by the server and connector unable to resume working we just resetting offset by setting gtid = null there so connector then fallbacks to binlog file/position and able to restart.

Proposal is: crate connector-level configuration option to disable GTID handling.

Implementation ideas (optional)

Configuration option allowing disable GTID handling making connector rely only on binlog file/position

Additional info:

Here we see that connector can fall back to binlog/postition in some cases