Update self version failure causes DDL to get stuck while MDL is disabled

[pcqz]

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

Similar to #43755, the difference is that MDL was disabled, and DDL job got stuck when tidb server failed to update schema version:

[2025/05/13 08:02:06.117 +08:00] [Info] [domain.go:215] ["diff load InfoSchema success"] [currentSchemaVersion=1217026] [neededSchemaVersion=1217027] ["start time"=14.630741ms] [phyTblIDs="[1398997,1399737]"] [actionTypes="[2048,2048]"]
[2025/05/13 08:02:08.118 +08:00] [Warn] [util.go:299] ["[ddl] etcd-cli put kv failed"] [key=/tidb/ddl/all_schema_versions/037a5fde-1b5e-4ad1-a2a0-dfa583e6bd5e] [value=1217027] [error="context deadline exceeded"] [retryCnt=0]
[2025/05/13 08:02:08.148 +08:00] [Info] [domain.go:517] ["update self version failed"] [oldSchemaVersion=1217026] [neededSchemaVersion=1217027] [error="context deadline exceeded"]

And DDL owner was continuously checking for unsynced versions

[2025/05/13 08:02:11.951 +08:00] [Info] [syncer.go:352] ["[ddl] syncer check all versions, someone is not synced, continue checking"] [ddl=/tidb/ddl/all_schema_versions/4e3becf5-9448-4cd6-9208-d845b0679638] [currentVer=1217026] [latestVer=1217027]
...
[2025/05/13 10:47:23.830 +08:00] [Info] [syncer.go:352] ["[ddl] syncer check all versions, someone is not synced, continue checking"] [ddl=/tidb/ddl/all_schema_versions/4e3becf5-9448-4cd6-9208-d845b0679638] [currentVer=1217026] [latestVer=1217027]

2. What did you expect to see? (Required)

DDL can update version after recovering from write failure.

3. What did you see instead (Required)

DDL execution is stuck, however, the workaround is simple, just execute another DDL.

4. What is your TiDB version? (Required)

v6.5.6

[pcqz]

/report customer