Fix a GBK test failure on DB runtimes[databricks]

[firestarman]

close #13800

The root cause is missing the check for DB runtimes when specifying the legacy charset config for the CSV read.

[firestarman]

build

[greptile-apps]

Greptile Summary

• Adds is_databricks_runtime() check to correctly set spark.sql.legacy.javaCharsets=true for GBK CSV test
• Fixes test failure on Databricks 14.3 runtime where legacy charset config was incorrectly set to false

Confidence Score: 5/5

• This PR is safe to merge with minimal risk
• The fix is a simple, targeted one-line change that adds a runtime check for Databricks. The change aligns with how Databricks backported the spark.sql.legacy.javaCharsets configuration from Spark 4.0.0, and directly addresses the reported test failure. The logic is correct and consistent with the existing pattern.
• No files require special attention

Sequence Diagram

sequenceDiagram
    participant Test as "test_csv_read_gbk_encoded_data"
    participant Runtime as "Runtime Check"
    participant Config as "Spark Config"
    participant CSV as "CSV Reader"
    
    Test->>Runtime: "Check is_spark_400_or_later() or is_databricks_runtime()"
    alt Spark 4.0+ or Databricks
        Runtime->>Config: "Set spark.sql.legacy.javaCharsets=true"
    else Earlier Spark version
        Runtime->>Config: "Set spark.sql.legacy.javaCharsets=false"
    end
    Test->>CSV: "Read GBK encoded CSV with config"
    CSV->>Test: "Return data"

Loading

[greptile-apps]

_{1 file reviewed, no comments}

_{Edit Code Review Agent Settings | Greptile
React with 👍 or 👎 to share your feedback on this new summary format}

[firestarman]

build