cluster-replication: add clock skew detection guards #82494
Description
We should detect if the destination cluster and source cluster are significantly skewed and warn or error, at least if we know the destination is behind enough that a reasonable cutover time might fall in the future, which could lead to some odd behaviors. We probably don't want to use the key timestamps since they can legitimately be in the future (e.g. global tables) so we'll probably want to just attach the current hlc to each streamed batch.
Jira issue: CRDB-16497