fix: ensure atomicity in create_lock_revision

[zhyass]

I hereby agree to the terms of the CLA available at: https://docs.databend.com/dev/policies/cla/

Summary

Guarantee atomic operations in create_lock_revision by combining the generation and insertion of revision into a single txn to prevent lock conflicts.

• Fixes bug: double lock ownership due to concurrent race #16906

Tests

• Unit Test
• Logic Test
• Benchmark Test
• No Test - Explain why

Type of change

• Bug Fix (non-breaking change which fixes an issue)
• New Feature (non-breaking change which adds functionality)
• Breaking Change (fix or feature that could cause existing functionality not to work as expected)
• Documentation Update
• Refactoring
• Performance Improvement
• Other (please describe):

---

This change is 

[drmingdrmer]

Reviewed 1 of 1 files at r1, all commit messages.
Reviewable status: all files reviewed, 1 unresolved discussion (waiting on @sundy-li and @zhyass)

---

src/meta/api/src/schema_api_impl.rs line 2751 at r1 (raw file):

            trials.next().unwrap()?.await;

            let revision = fetch_id(self, id_generator.clone()).await?;

Do not fetch id. just self.get() to get the current value of id_generator, and update it in the transaction. fetch_id update the value at once.

[drmingdrmer]

Reviewed 1 of 1 files at r2, all commit messages.
Reviewable status: complete! all files reviewed, all discussions resolved (waiting on @sundy-li)