Reframe ReplaceTableTransaction.commit_transaction docstring

Per audit: clarify that we always emit AssertLastAssigned*Id, which is
stricter than the reference contract that conditions them on Add*
being present. Fail-safe vs corruption-risk.

Author: smaheshwar-pltr

pyiceberg/table/__init__.py

@@ -1132,13 +1132,18 @@ def _find_matching_sort_order_id(table_metadata: TableMetadata, sort_order: Sort
     def commit_transaction(self) -> Table:
         """Commit the replace changes to the catalog.
 
-        Requirements:
+        Always emits three optimistic-concurrency requirements:
         - `AssertTableUUID` — the table identity hasn't changed since load.
         - `AssertLastAssignedFieldId` — guards against a concurrent commit bumping
           `last-column-id` between load and commit (which would cause our newly-assigned
           field IDs to collide).
         - `AssertLastAssignedPartitionId` — same guard for partition field IDs.
 
+        Note: this is deliberately stricter than the reference REST `forReplaceTable`
+        contract, which conditions the `AssertLastAssigned*Id` requirements on
+        `AddSchema` / `AddPartitionSpec` being present in the change set. Emitting them
+        unconditionally is fail-safe — a no-op replace just confirms the assertions hold.
+
         Returns:
             The table with the updates applied.
         """