Extend syntax for Dynamic Catalogs

[ssheikin]

Description

• Add ALTER CATALOG commands to change name, properties and owner with security checks
  RENAME, SET PROPERTIES implemented
  catalog owner is not supported yet.
  catalog comment is not supported yet.

Additional context and related issues

Trino epic #12709

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:

# Section
* Add support for CREATE CATALOG LIKE statement. ({issue}`22188`)
* Add support for SHOW CREATE CATALOG statement. ({issue}`22188`)
* Add support for ALTER CATALOG RENAME statement. ({issue}`22188`)
* Add support for ALTER CATALOG SET PROPERTIES statement. ({issue}`22188`) 

[ssheikin]

@martint @dain @kokosing @nineinchnick @SemionPar please review

[ebyhr]

The current implementation exposes all properties even if it's marked as @ConfigHidden or @ConfigSecuritySensitive. I think we should hide or redact such properties.

[nineinchnick]

@ssheikin could you maybe extract SHOW CREATE CATALOG to a separate PR? @martint would that help with getting the less controversial parts merged sooner?

[piotrrzysko]

I have removed SHOW CREATE CATALOG from this PR. It should be possible to re-add it once the following are merged:

• Add connector SPI for returning redactable properties #24562
• Redact sensitive information in catalog queries #24563

I'm not sure if we want to introduce CREATE CATALOG LIKE (at least not at this stage). One question that comes to mind is how to define access rules for it. According to the SQL specification for CREATE TABLE LIKE:

If a <like clause> is contained in a <table definition>, then the applicable privileges for A shall include
SELECT privilege on the table identified in the <like clause>.

The issue is that we don’t have a SELECT privilege for catalogs.
I’m also not aware of any databases that provide CREATE ... LIKE functionality for anything other than tables. This makes it difficult to infer whether there’s a common approach we could adopt in this scenario.

[github-actions]

This pull request has gone a while without any activity. Tagging the Trino developer relations team: @bitsondatadev @colebow @mosabua

[mosabua]

I am adding the stale-ignore label under the assumption that you are still driving this PR to completion @ssheikin

[ebyhr]

Did you omit lowercase intentionally?

trino> CREATE CATALOG test USING memory;
CREATE CATALOG
trino> ALTER CATALOG test RENAME TO TEST;
RENAME CATALOG
trino> show catalogs;
 Catalog
---------
 TEST
 memory
 system
 tpch
(4 rows)

[piotrrzysko]

I think it was unintentional. I updated it to match how other catalog statements work.

[piotrrzysko]

Current status of this PR: it will no longer include SHOW CREATE CATALOG and CREATE CATALOG LIKE. The former will likely be re-added once redacting security-sensitive information (#24563) is merged. The latter probably needs more discussion. I don’t have permissions to update the PR description. Could one of the maintainers or @ssheikin update it?

[kokosing]

I have updated the description