feat: Implement lock component for ProcedureManager

[evenyag]

I hereby agree to the terms of the GreptimeDB CLA

What's changed and what's your intention?

This PR introduces a lock component for ProcedureManager. To implement lock, it also needs a ProcedureMeta struct to track the metadata of a procedure in the manager.

LockMap manages all locks and it uses struct Lock to represent a lock entry.

struct Lock {
    /// Current lock owner.
    owner: ProcedureMetaRef,
    /// Waiter procedures.
    waiters: VecDeque<ProcedureMetaRef>,
}

Only the owner procedure can hold the lock. Once it releases the lock, the lock entry pops the waiter from the queue and notifies the waiter procedure.

Checklist

• I have written the necessary rustdoc comments.
• I have added the necessary unit tests and integration tests.

Refer to a related PR or issue link (optional)

• Tracking issue for the procedure framework #286

[codecov]

Codecov Report

Merging #937 (2811f4c) into develop (fc9276c) will increase coverage by 0.09%.
The diff coverage is 97.31%.

@@             Coverage Diff             @@
##           develop     #937      +/-   ##
===========================================
+ Coverage    85.85%   85.95%   +0.09%     
===========================================
  Files          441      443       +2     
  Lines        59053    59202     +149     
===========================================
+ Hits         50700    50885     +185     
+ Misses        8353     8317      -36     

Flag	Coverage Δ
rust	85.95% <97.31%> (+0.09%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files	Coverage Δ
src/common/procedure/src/lib.rs	100.00% <ø> (ø)
src/common/procedure/src/local.rs	95.00% <95.00%> (ø)
src/common/procedure/src/local/lock.rs	98.16% <98.16%> (ø)
src/object-store/src/test_util.rs	0.00% <0.00%> (-100.00%)	⬇️
src/datanode/src/instance.rs	47.11% <0.00%> (-10.67%)	⬇️
tests-integration/src/test_util.rs	80.68% <0.00%> (-8.72%)	⬇️
src/frontend/src/table/scan.rs	85.18% <0.00%> (-5.56%)	⬇️
src/servers/src/auth/user_provider.rs	81.81% <0.00%> (-2.28%)	⬇️
src/servers/src/postgres/handler.rs	82.84% <0.00%> (-0.37%)	⬇️
src/datatypes/src/data_type.rs	97.91% <0.00%> (-0.35%)	⬇️
... and 8 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

[MichaelScofield]

Seems the lock implementation has some complex mechanism, specifically how the locks are propagated from parents to children. Not found in RFC. Can you give a more thorough explanation behind the design choice?

[evenyag]

Not found in RFC.

See the locking part

Sub-procedures always inherit their parents' locks. The ProcedureManager only acquires locks for a procedure if its parent doesn't hold the lock.

But this PR doesn't implement this. We use this to avoid recursive locking.

[evenyag]

You could refer to the PoC for the full prototype.

@MichaelScofield