[#28705] docdb: Disable table level lock for ConcurrentDDLAnalyze test

Summary:
Disable enable_object_locking_for_table_locks for 'ConcurrentDDLAnalyze' test.
This test was designed to verify that a long-running ANALYZE operation can be interrupted by a concurrent DDL. However, with table-level locking enabled, this is no longer the case, ANALYZE acquires a table lock that blocks the other DDL from proceeding
Jira: DB-18408

Test Plan: ./yb_build.sh --cxx-test pgwrapper_pg_auto_analyze-test --gtest_filter PgConcurrentDDLAnalyzeTest.ConcurrentDDLAnalyze

Reviewers: myang, sanketh, rthallam

Reviewed By: sanketh

Subscribers: yguan, yql, ybase

Differential Revision: https://phorge.dev.yugabyte.com/D47023

Author: yusong-yan

src/yb/yql/pgwrapper/pg_auto_analyze-test.cc

@@ -1243,6 +1243,11 @@ class PgConcurrentDDLAnalyzeTest : public LibPqTestBase {
     // we want to trigger ANALYZE explicitly similar to what auto analyze would have
     options->extra_tserver_flags.push_back("--ysql_enable_auto_analyze=false");
     options->extra_tserver_flags.push_back("--ysql_yb_user_ddls_preempt_auto_analyze=true");
+    // The test verifies a long ANALYZE can be interrupted by another DDL. However, table lock
+    // prevents this so we're disabling it to keep the test's original intent.
+    options->extra_tserver_flags.emplace_back(
+        "--allowed_preview_flags_csv=enable_object_locking_for_table_locks");
+    options->extra_tserver_flags.emplace_back("--enable_object_locking_for_table_locks=false");
     ANNOTATE_UNPROTECTED_WRITE(FLAGS_vmodule) = "libpqutils*=1";
   }
 };