SchemaUpdate cannot move a column by its new name after renameColumn in the same update

### Query engine

It does not matter.

### Question

When using `UpdateSchema`, I noticed a column cannot be moved(or any other similar operation) by its new name after it has been renamed in the same SchemaUpdate.

For example:

```java
Schema newSchema =
new SchemaUpdate(schemaWithIdentifierFields, SCHEMA_LAST_COLUMN_ID)
.renameColumn("data", "data_renamed")
.moveFirst("data_renamed")
.apply();
```

This fails with: Cannot move missing column: data_renamed.(Actually I have to use the original name `data` in `moveFirst` method).

Is this the intended behavior of UpdateSchema, where subsequent operations in the same update should continue to refer to renamed columns by their original names? Or should SchemaUpdate also allow resolving
pending renamed names for move operations within the same update?

Start in the SchemaUpdate implementation and trace how renameColumn and moveFirst resolve column names when chained in one update. Reproduce the provided rename-then-move example, then inspect existing schema-update tests or add a focused regression case; done should establish and verify the intended behavior for the renamed name.

Written by the indexing model from the issue text.