[Binlog][Local] Publish metadata retry repeatedly appends paired correction segments

## Problem

[Binlog][Local] Publish metadata retry repeatedly appends paired correction segments

## Minimal reproduction path

In a local ROW Binlog workload, make a publish metadata response unavailable after the first publish attempt and trigger the retry path. Inspect the resulting base and companion rowsets. Verify that retries converge to one paired correction segment rather than repeatedly appending correction segments.

## Expected result

Publish metadata retries are idempotent and produce one paired correction segment.

## Source

This report is a sanitized tracking record for Jira DORIS-28071. Internal hosts, paths, artifacts, build identifiers, and private logs are intentionally omitted.

No files or tests are named. Reproduce the local ROW Binlog scenario, then trace the publish-metadata retry path and inspect the resulting base and companion rowsets. Done means retries are idempotent and converge to one paired correction segment instead of repeatedly appending segments.

Written by the indexing model from the issue text.