Debezium Informix connector task remains RUNNING but does not produce CDC events after Informix restart until task is explicitly restarted

## Description

We are using the Debezium Informix connector with Kafka Connect to capture CDC events from an Informix database.

During our monthly maintenance procedure, we restart the Informix database and reset/clear the related offset. After the database is fully back online, we resume and restart the Debezium connector.

However, we observed that even though both the connector and its task are reported as `RUNNING` by the Kafka Connect REST API, CDC events are not produced to the Kafka topic.

The CDC flow only resumes after we explicitly restart the connector task.

## Observed Behavior

After the Informix database restart and Debezium connector restart:

1. `connector.state` is reported as `RUNNING`
2. `tasks[x].state` is reported as `RUNNING`
3. No obvious task error is shown in the connector status output
4. Test data changes in Informix are successfully committed
- `INSERT`
- `UPDATE`
- `DELETE`
5. However, the Kafka topic does not receive any corresponding CDC events

After explicitly restarting the connector task, CDC events are produced to Kafka again.

## Expected Behavior

If the connector and task are both reported as `RUNNING`, the connector task should actively resume CDC processing and produce committed Informix data changes to the Kafka topic.

Alternatively, if the task is not actually processing CDC events after the Informix restart, the task state should not remain `RUNNING`, or there should be an error / warning indicating that the task needs to be restarted.

## Actual Behavior

The connector and task appear healthy from the Kafka Connect REST API, but CDC event delivery is not working.

The following conditions were confirmed:

```text
connector.state = RUNNING
tasks[x].state = RUNNING
Informix test INSERT / UPDATE / DELETE transactions were committed successfully
Kafka topic did not receive the corresponding CDC events