feat(meta): implement distributed semaphore based on meta-service

[drmingdrmer]

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

Summary

feat(meta): implement distributed semaphore based on meta-service

This commit introduces a distributed semaphore implementation that provides
reliable resource management across distributed systems. The semaphore is
built on top of meta-service and offers:

• Fair queueing mechanism using sequence numbers
• Automatic lease management with TTL
• Atomic operations for consistency
• Real-time updates via meta-service watch API

Usage:

let client = MetaGrpcClient::try_create(/*..*/);
let acquired_guard = Semaphore::new_acquired(
        client,
        "your/semaphore/name/in/meta/service",
        2,                          // capacity: 2 acquired at most
        "id11",                     // ID of this acquirer
        Duration::from_secs(3)      // lease time
).await?;

acquired_guard.await;
// Released

The implementation uses a queue-based structure with sequence numbers to
ensure fair ordering of resource requests. It handles distributed
coordination through meta-service, providing automatic lease extension
and cleanup of stale entries.

Key components:

• Semaphore: Main entry point for semaphore operations
• Acquirer: Handles the acquisition process
• AcquiredGuard: Manages semaphore lifecycle
• Queue-based storage with sequence numbers

Note: Current version sets capacity per client. Future versions will
store capacity in meta key for global consistency.

docs: update meta-service change-log

Tests

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

Type of change

• Other

Related Issues

---

This change is 

[drmingdrmer]

@zhang2014

The CI may still need to be fixed, but the PR implementation is now complete. I invite you to review the API layer specifically to ensure it aligns with your requirements and expectations.

And if you got time, I'd also appreciate your feedback on the other components of this implementation. Any additional review would be valuable.

[drmingdrmer]

Reviewed 1 of 1 files at r1, 17 of 34 files at r2, 3 of 10 files at r3, 12 of 17 files at r4, 4 of 4 files at r5, 5 of 5 files at r6, 10 of 10 files at r7, 6 of 6 files at r8, 4 of 4 files at r9, 5 of 5 files at r10, all commit messages.
Reviewable status: complete! all files reviewed, all discussions resolved (waiting on @drmingdrmer)