[Bugfix] Populate table name from the identifier in Iceberg conversion

[jalpan-randeri]

What is the purpose of the pull request

While converting the iceberg table to other format such as Hudi, the icerberg source table do not populate the table name. This is due to iceberg table's behavior as it is treated as Hadoop tables. This leads to table identified as table-location, leading to confusing conversation.

BUG= #494

Brief change log

This commit handles the conversation logic, when icebege table manager provides HadoopTable, it populate the table name from provided input TableIdentifier. This ensures that source table name is carried over to the transformation.

Verify this pull request

• Updated unit test to cover this scenario.

Manual Verification

#### Step 1. create iceberg table
./bin/spark-shell --packages org.apache.iceberg:iceberg-spark-runtime-3.5_2.12:1.7.0\                                                                  
    --conf spark.sql.extensions=org.apache.iceberg.spark.extensions.IcebergSparkSessionExtensions \
    --conf spark.sql.catalog.spark_catalog=org.apache.iceberg.spark.SparkSessionCatalog \
    --conf spark.sql.catalog.spark_catalog.type=hive \
    --conf spark.sql.catalog.local=org.apache.iceberg.spark.SparkCatalog \
    --conf spark.sql.catalog.local.type=hadoop \
    --conf spark.sql.catalog.local.warehouse=$PWD/warehouse \
    --conf spark.sql.defaultCatalog=local

spark.sql(""" 
CREATE TABLE prod.db.sample (
 id bigint NOT NULL COMMENT 'unique id',
 data string)
USING iceberg 
""").show()

spark.sql("INSERT INTO prod.db.sample VALUES (1, 'jalpan) ").show()

#### Step 2. create xtable config
$ cat xtable_iceberg.yaml

sourceFormat: ICEBERG
targetFormats:
  - HUDI
datasets:
  -
    tableBasePath: /Users/jalpan/workspace/spark/warehouse/prod/db/sample
    tableName: sample

#### Step 3. perform sync
java -jar xtable-utilities/target/xtable-utilities_2.12-0.2.0-SNAPSHOT-bundled.jar --datasetConfig xtable_iceberg.yaml

#### Step 4. validate 
cat /Users/jalpan/workspace/spark/warehouse/prod/db/sample/.hoodie/hoodie.properties | grep name                                                                                      [14:21:05]
hoodie.table.name=sample

[the-other-tim-brown]

LGTM! Can you squash down to a single commit?

[ashvina]

Could you please confirm if existing tests cases cover both the paths?