feat(frontend, meta): support RECOVER command to trigger recovery

[kwannoel]

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

What's changed and what's your intention?

Closes #14700

The current shortcoming of this approach is that while recovery is triggered, the command does not wait for recovery to complete, it operates in an async way. Welcome any ideas for improvement. If not we can improve it later.

Path of recover command:

Frontend -> Meta Client -> Stream Manager -> Notification Service -> Barrier Manager -> trigger recovery

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

The user can use the command: RECOVER to trigger an adhoc recovery. This can be used in cases where barrier latency is high, and we want to force a recovery to kick-in, so commands like cancel, drop can immediately take effect.

[yezizp2012]

LGTM, thx for the PR.