Summary:
Commit 08188f9b introduced a mechanism to serializable DDLs early via
acquisition of a `FOR UPDATE` lock on the catalog version row for the
database. This causes spurious conflict errors even with a single connection
executing DDLs sequentially (see gh issue #27293). Until we fix #27293,
this change disables yb_force_early_ddl_serialization by default.
Jira: DB-17355

Test Plan:
Jenkins: urgent

The issue is seen in the `test_cross_db_concurrent_ddls` stress test, this issue will resolve conflict errors seen by DDLs in that test. When we fix #27293, we will add a unit test to reproduce the issue.

./yb_build.sh release --cxx-test pgwrapper_pg_auto_analyze-test --gtest_filter PgAutoAnalyzeTest.DDLsInParallelWithAutoAnalyze

Reviewers: smishra, myang

Reviewed By: myang

Subscribers: yql

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