Possible read-after-write consistency issue with multiple schema migration steps in Iceberg tables on AWS Glue + S3

### Apache Iceberg version

Pyiceberg 0.10.0
Pyiceberg-core 0.6.0

### Please describe the bug 🐞

This may be a hard one to pin down but I noticed that multiple schema migration steps executed sequentially in the same `update_schema` context *sometimes* result in Exceptions like column name not found when using Iceberg tables on AWS Glue. An example:

```python
with table.update_schema() as update:
update.rename_column("some_column", "renamed_column")
update.move_first("renamed_column") # this sometimes fails with an error
# that renamed column doesn't exist
```

I have not noticed it with other back-ends like SQLite, leading me to believe it is a Glue issue specifically where a write may not yet be reflected by the time of the next operation.

### Willingness to contribute

- [ ] I can contribute a fix for this bug independently
- [x] I would be willing to contribute a fix for this bug with guidance from the Iceberg community
- [ ] I cannot contribute a fix for this bug at this time

table.update_schema() のフローから始め、rename_column に続けて move_first を実行する例を AWS Glue と S3 に対して再現し、SQLite と比較してください。次の操作の前に最初のスキーマ書き込みが可視になっているかを追跡してください。不整合を説明し、回帰テストを追加するか、残っているバックエンドの制限を明確に文書化できれば完了です。

索引モデルが issue の本文から書いたものです。