Remove location from SHOW CREATE TABLE for translated table

[Kundannitp]

Fixes #28483

Currently, the SHOW CREATE TABLE command for the Hive connector returns the managed table's path as external_location. This causes confusion as to whether the table is actually managed or external, violating the Principle of Least Surprise.

This change restricts the external_location property from being printed for managed tables that were silently translated to external tables by Hive.

Additional context and related issues
Previously, the if condition only checked if the table type was EXTERNAL_TABLE before appending the external_location property to the DDL.

However, in Hive 3.x+, Hive intercepts non-transactional managed table creations and silently converts them to external tables to bypass ACID requirements. When doing so, Hive marks the table parameter "TRANSLATED_TO_EXTERNAL" as "true".

To fix this, we now explicitly check this parameter. If the table is external but was translated by Hive, we treat it as a managed table for the purpose of SHOW CREATE TABLE and omit the external_location property.

Release notes
( ) This is not user-visible or is docs only, and no release notes are required.
( ) Release notes are required. Please propose a release note for me.
(x) Release notes are required, with the following suggested text:

Hive Connector

• Fix SHOW CREATE TABLE exposing external_location for managed tables. ({issue}28483)

[cla-bot]

Thank you for your pull request and welcome to the Trino community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. Continue to work with us on the review and improvements in this PR, and submit the signed CLA to cla@trino.io. Photos, scans, or digitally-signed PDF files are all suitable. Processing may take a few days. The CLA needs to be on file before we merge your changes. For more information, see https://github.com/trinodb/cla

[ebyhr]

Could you please add a test?

[Kundannitp]

@ebyhr Thanks for the review.
Actually tests are already present for this scenario but the error can only be observed if tests run on a actual hive and trino server. Please refer this #28483 (comment) for why its not captured in current tests.
So not sure if we can add a test which will run on a real setup.
If you can point out any scenario where such a test added I can use it as a reference.

[ebyhr]

@Kundannitp We already have test classes (e.g. BaseTestHiveOnDataLake) with dockerized Hive.

[Kundannitp]

okay thanks
Let me check

[cla-bot]

Thank you for your pull request and welcome to the Trino community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. Continue to work with us on the review and improvements in this PR, and submit the signed CLA to cla@trino.io. Photos, scans, or digitally-signed PDF files are all suitable. Processing may take a few days. The CLA needs to be on file before we merge your changes. For more information, see https://github.com/trinodb/cla

[cla-bot]

Thank you for your pull request and welcome to the Trino community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. Continue to work with us on the review and improvements in this PR, and submit the signed CLA to cla@trino.io. Photos, scans, or digitally-signed PDF files are all suitable. Processing may take a few days. The CLA needs to be on file before we merge your changes. For more information, see https://github.com/trinodb/cla

[Kundannitp]

@ebyhr
Thanks for pointing out the correct test file.
Added tests, pls check