Add register_table procedure support for delta table

[krvikash]

Description

Fixes #13568

1. Procedure call -> delta.system.register_table(shcema_name => 'testdb', table_name => 'table1', table_location => 's3://my-bukcet/a/path/')
2. By default CREATE TABLE with(location='***') will not allow to register table using existing location.
3. Enable via delta.create-table-with-existing-location.enabled config property or create_table_with_existing_location_enabled session property to allow user to register table using CREATE TABLE statement (This support will be removed permanently after some release)
4. By default register_table procedure is disabled. Enable it via delta.allow-register-table-procedure config property

Non-technical explanation

NA

Release notes

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

# Delta Lake
* Allow registering existing table files in the metastore with the new
  [`register_table` procedure](delta-lake-register-table). ({issue}`13568`)
* Deprecate creating a new table with existing table content.
  This can be enabled using the `delta.legacy-create-table-with-existing-location.enabled`
  config property or `legacy_create_table_with_existing_location_enabled` session property. ({issue}`13568`)

[alexjo2144]

Do you have a test that shows the legacy syntax can be re-enabled?

[alexjo2144]

You could also just create the table using the Hive or Iceberg connectors, if you have one of those catalogs configured for the test

CREATE TABLE hive.schema.table_name ...

[krvikash]

Just to confirm that I understand correctly, We can create a table using Hive or Iceberg connectors to verify the delta test cases where delta logs are missing?

[krvikash]

Do you have a test that shows the legacy syntax can be re-enabled?

No, Not yet. I will add the test case for this.

[krvikash]

rebased and addressed comments.

[krvikash]

rebased and added BaseDeltaLakeConnectorSmokeTest#testRegisterTableWithTrailingSlashLocation

[findinpath]

LGTM % some minor test related improvements.

[ebyhr]

CI hit #15173

[hangc0276]

When I registered a delta table with an existing path and the new data kept writing to the path, I used SQL to query the data from the table and found it couldn't load new data.

I register a new table with the same path, and new data can be queried out.

Is it the expected behavior? @ebyhr @krvikash

[findinpath]

@hangc0276 pls sketch your scenario in a new github issue - your question is not related to this PR.

To be taken into account when writing the new issue

... and the new data kept writing to the path

Was writing in the newly registered table happening through INSERT / UPDATE / MERGE operations via Trino/Spark or rather at the file level ?