Simplify SEA disposition: use connection parameters instead of statement type

[gopalldb]

Summary

The SEA result disposition (INLINE vs EXTERNAL_LINKS) was determined by statement type — only QUERY/SQL/METADATA got cloud fetch, while DML/DDL was forced to INLINE regardless of connection config. This is incorrect; disposition should be driven purely by connection parameters.

Changes

• DatabricksSdkClient.useCloudFetchForResult(): Removed StatementType parameter. Now based solely on shouldEnableArrow() && isCloudFetchEnabled() (the EnableQueryResultDownload connection property).
• All statement types get the same disposition based on what the user configured.

Before

private boolean useCloudFetchForResult(StatementType statementType) {
    return this.connectionContext.shouldEnableArrow()
        && (statementType == StatementType.QUERY
            || statementType == StatementType.SQL
            || statementType == StatementType.METADATA);
}

After

private boolean useCloudFetchForResult() {
    return this.connectionContext.shouldEnableArrow()
        && this.connectionContext.isCloudFetchEnabled();
}

Test plan

• testDisposition_arrowAndCloudFetchEnabled_usesExternalLinks — verifies ARROW_STREAM format and non-INLINE disposition when both configs enabled
• testDisposition_cloudFetchDisabled_usesInline — verifies INLINE disposition when cloud fetch is disabled
• Full test suite + integration tests

NO_CHANGELOG=true

This pull request was AI-assisted by Isaac.