feat(barrier): maintain per database scheduled command queue

[wenym1]

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.

What's changed and what's your intention?

To support database failure isolation, we may temporarily block the command queue of a specific database when we are recovering the database, like what we do globally in the global recovery. Therefore, in this PR, we change to maintain per database scheduled command queue, and each queue have its own status, and we will support mark the queue as ready or blocked in either per-database manner or globally.

Checklist

• I have written necessary rustdoc comments
• I have added necessary unit tests and integration tests
• I have added test labels as necessary. See details.
• I have added fuzzing tests or opened an issue to track them. (Optional, recommended for new SQL features Sqlsmith: Sql feature generation #7934).
• My PR contains breaking changes. (If it deprecates some features, please create a tracking issue to remove them in the future).
• All checks passed in ./risedev check (or alias, ./risedev c)
• My PR changes performance-critical code. (Please run macro/micro-benchmarks and show the results.)

• My PR contains critical fixes that are necessary to be merged into the latest release. (Please check out the details)

Documentation

• My PR needs documentation updates. (Please use the Release note section below to summarize the impact on users)

Release note

If this PR includes changes that directly affect users or other significant modifications relevant to the community, kindly draft a release note to provide a concise summary of these changes. Please prioritize highlighting the impact these changes will have on users.

[wenym1]

• feat(meta): support reload runtime info of single database #19597
• feat(barrier): maintain per database scheduled command queue #19592 👈 (View in Graphite)
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[yezizp2012]

LGTM