Remote TLogs do not need to fsync every version

The remote logs commit and fsync every version just like the primary logs, however they do not have the same latency sensitivity as the primary logs.

We could instead commit every half second like the storage servers to improve performance.

No file or test is named. Start by locating the remote-log commit and fsync path, then compare its timing behavior with the storage servers mentioned in the issue. Done means remote logs no longer fsync every version and commit on roughly a half-second cadence, with the performance impact checked.

Written by the indexing model from the issue text.