Do not run Hive and Delta compatibility tests on Databricks

[findinpath]

Description

Test against Delta Lake OSS gives enough certainty for the accuracy
of the Delta Lake connector.

Relates to #18805

Additional context and related issues

Release notes

(x) This is not user-visible or is docs only, and no release notes are required.

[ebyhr]

Do we still need hive.properties in AbstractSinglenodeDeltaLakeDatabricks & singlenode-delta-lake-databricks directory and also delta.hive-catalog-name=hive in delta.properties?

[findinpath]

Do we still need hive.properties in AbstractSinglenodeDeltaLakeDatabricks & singlenode-delta-lake-databricks directory and also delta.hive-catalog-name=hive in delta.properties?

I'm trying to figure out whether we need

trino/testing/trino-product-tests/src/main/java/io/trino/tests/product/deltalake/TestDatabricksWithGlueMetastoreCleanUp.java

Line 66 in b8f77ae

onTrino().executeQuery("SET SESSION hive.hive_views_legacy_translation = true");

Let's handle this in a follow-up PR to focus solely on this aspect.
In any case TestDatabricksWithGlueMetastoreCleanUp should be probably executed only once per build, not for every databricks product test.

Idea for smoke test to legitimate existence of hive.properties: We could have a hive and delta lake compatibility test where we can observe whether Hive tables (USING parquet) created via Databricks are readable through the hive connector.