Added new configuration to pass catalog name to metastore when creati…

[AnuragKDwivedi]

Description

This PR introduces a new configuration that can be applied to Hive, Hudi, Delta, and Iceberg catalog properties. The configuration enables the catalog name to be passed to the metastore, significantly enhancing the metastore's capabilities for managing and organizing schemas and tables based on the catalog name.

By passing the catalog name, the metastore can now support unique schema creation under different catalogs, as it already recognizes the combination of catalog and schema as unique. Additionally, this change allows the metastore to filter schemas at the metastore layer itself, making schema management more efficient.

Motivation and Context

Previously, due to the absence of the catalog name in metastore interactions, all schemas were created under the default "hive" catalog. This limitation made it impossible for users to filter or retrieve schemas associated with a specific catalog. The metastore lacked the ability to distinguish between schemas created under different catalogs.

With this update:

• Schemas can now be managed and organized by catalog, leveraging the metastore's existing support for catalog-schema uniqueness.
• Users can create schemas with the same name under different catalogs, enabling better schema organization and reducing naming conflicts.
• Schema filtering at the metastore layer becomes possible, providing more accurate and efficient responses to schema queries.
  This change addresses a long-standing limitation and significantly improves schema management in environments using Hive, Hudi, Delta, and Iceberg catalogs.

#22895

Impact

NA

Test Plan

CI passed

Contributor checklist

• Please make sure your submission complies with our development, formatting, commit message, and attribution guidelines.
• PR description addresses the issue accurately and concisely. If the change is non-trivial, a GitHub Issue is referenced.
• Documented new properties (with its default value), SQL syntax, functions, or other functionality.
• If release notes are required, they follow the release notes guidelines.
• Adequate tests were added if applicable.
• CI passed.

== RELEASE NOTES ==
General Changes
Added configuration to pass catalog names to the metastore, enabling catalog-based schema management and filtering.

[prestodb-ci]

Saved that user @AnuragKDwivedi is from IBM

[steveburnett]

Consider adding documentation for this configuration property. Perhaps in https://github.com/prestodb/presto/blob/master/presto-docs/src/main/sphinx/admin/properties.rst.

[steveburnett]

New release note guidelines as of last week: PR #24354 automatically adds links to this PR to the release notes. Please remove the manual PR link in the following format from the release note entries for this PR.

:pr:`12345`

I have updated the Release Notes Guidelines to remove the examples of manually adding the PR link.