fix(rpl): add clock_diff_with_master to sql_delay_event commit-timestamps path

[jiyfhust]

fix(rpl): add clock_diff_with_master to sql_delay_event commit-timestamps path

PROBLEM

In sql_delay_event(), when immediate_commit_timestamp is available from the GTID event, the calculated sql_delay_end does not include clock_diff_with_master:

sql_delay_end = ceil(immediate_commit_timestamp / 1000000.00) + sql_delay;

However, the fallback path (when commit timestamps are unavailable) correctly adds clock_diff_with_master:

sql_delay_end = when.tv_sec + clock_diff_with_master + sql_delay;

Since immediate_commit_timestamp is in the master's clock domain but nap_time is computed against time(nullptr) (the replica's clock), the missing clock_diff_with_master causes the delay calculation to be off by the clock difference between master and replica. For example, if the master clock is 60 seconds ahead of the replica, the replica will wait 60 seconds less than the configured SOURCE_DELAY.

FIX

Add clock_diff_with_master to the commit-timestamps code path, making it consistent with the fallback path:

sql_delay_end = ceil(immediate_commit_timestamp / 1000000.00)
+ clock_diff_with_master + sql_delay;

This ensures correct delayed replication behavior when master and replica clocks are not synchronized.

The fix is backward compatible: when clock_diff_with_master is 0 (master and replica clocks are synchronized), behavior is unchanged.

What does this change do?

Why is it needed?

How was it tested?

• Added/updated MTR tests under mysql-test/
• scripts/ci/mtr.sh passes locally
• Ran the relevant full suite (name it): ______

Contributor checklist

• Code is formatted (scripts/ci/format.sh)
• Commits are focused with descriptive messages

AI assistance

• I did not use AI assistance for this contribution
• I used AI assistance for this contribution

If AI assistance was used, describe the tool(s) and extent of use:

Areas touched