Iceberg: Keep iceberg properties in sync with hms properties

In HIVE-26596, as we have not implement all COW mode, we enforced mor mode for iceberg v2 table in the tow scenarios:

1. create a v2 iceberg table, the delete mode will be set mor if not specified
2. upgrage v1 table to v2, and the delete mode will be set mor

In HS2, we check the mode(cow/mor) from hms table properties instead of iceberg properties(metadata json file), and HIVE-26596 only change hms table properties.  Therefore, it is ok for HS2 to operate iceberg table by checking cow/mor mode from hms properties, but for others like Spark, they operate the iceberg table by checking cow/mor from iceberg properties(metadata json file).

Before we implement all COW mode, we need keep iceberg properties in sync with hms properties to  make the users have the same experience on multiple engines(HS2 & Spark).