[#29224] DocDB: Enable object locking feature on by default for release builds

Summary: This revision enables object locking feature on by default for release builds. This will help get additional validation from QA runs. Keeping it disabled in non release builds for now to continue getting test coverage for the feature off scenario.

Test Plan: Jenkins

Reviewers: rthallam, amitanand

Reviewed By: rthallam, amitanand

Subscribers: ybase, yql

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

Author: basavaraj29

src/yb/common/common_flags.cc

@@ -215,7 +215,13 @@ DEFINE_RUNTIME_uint64(refresh_waiter_timeout_ms, 30000,
 TAG_FLAG(refresh_waiter_timeout_ms, advanced);
 TAG_FLAG(refresh_waiter_timeout_ms, hidden);
 
-DEFINE_NON_RUNTIME_bool(enable_object_locking_for_table_locks, false,
+#ifdef NDEBUG
+constexpr bool kEnableObjectLockingForTableLocks = kEnableDdlTransactionBlocks;
+#else
+constexpr bool kEnableObjectLockingForTableLocks = false;
+#endif
+DEFINE_NON_RUNTIME_bool(enable_object_locking_for_table_locks,
+    kEnableObjectLockingForTableLocks,
     "This flag enables the object lock APIs provided by tservers and masters - "
     "AcquireObject(Global)Lock, ReleaseObject(Global)Lock. These APIs are used to "
     "implement pg table locks.");