[Binlog][Cloud] VISIBLE retry loses version outcome and permits stale read after Table Stream commit

## Problem

[Binlog][Cloud] VISIBLE retry loses version outcome and permits stale read after Table Stream commit

## Minimal reproduction path

In a Cloud Table Stream workload, make the response of a VISIBLE operation unavailable after the commit is durable and execute the retry path. Read the stream immediately after recovery and after a fresh metadata lookup. Verify that the retry returns the durable version outcome and never permits a stale read after the stream commit.

## Expected result

VISIBLE retry reports the durable version and subsequent reads are not stale.

## Source

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

No source files or tests are named. Start with the minimal reproduction: make the VISIBLE response unavailable after a durable commit, then trace the retry path, recovery read, and fresh metadata lookup for the Cloud Table Stream. Done means the retry reports the durable version and subsequent stream reads are not stale.

Written by the indexing model from the issue text.