[ADH-8380] Iceberg table rename PoC: implement metadata file rename

[tigrulya-exe]

Changes

• New catalog flag rename.metadata.location.update (false by default), currently supported only by HMS catalog. When true, HiveCatalog also re-points the Iceberg metadata location to the new name's default warehouse path so that post-rename writes land under the new prefix.
• The rename is performed atomically in a single HMS alter_table RPC.
• Purging table with a drop.base-directory.enabled option now always runs the per-file purge first (behavior of drop.base-directory.enabled set to false), and only then attempts to delete the base table directory. The directory is removed only when nothing remains under the prefix, otherwise the directory is preserved. It allows a table with rename.metadata.location.update set to true survive scenarios, when another table, sitting in the previous location of the original table, is purged.
• Added Spark tests to check the aforementioned rename, then re-create old name, then drop the new old-name with PURGE scenario.
• Rename only re-points the metadata location, it does not physically move data files. Anything written before the rename keeps absolute paths under the old src directory and depends on that directory continuing to exist.
• Only tables sitting at the default warehouse path are relocated, tables with an explicit LOCATION fall back to current plain rename behavior.

Limitations

• External directory-level deletes are out of scope. A filesystem-level rm -rf, purging of another non-Iceberg Hive table sitting in the old directory, or any directory deletion that does not go through the Iceberg catalog has no protection and can cause errors, because relocated metadata file still points to the old directory.
• RENAME_UPDATE_METADATA_LOCATION is Hive-catalog only. The flag is opt-in and implemented for HiveCatalog. Other catalogs (REST, JDBC, Glue, Nessie) are not touched in this PR.
• Current implementation fallbacks to the old behavior (rename only table) in case if table has custom write-path properties (write.data.path, write.metadata.path, write.location-provider.impl, write.object-storage.path, write.folder-storage.path)