feat: add graph check in risectl for sql meta store

[shanicky]

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

What's changed and what's your intention?

run ctl meta graph-check

If there are no issues, it will exit with status code 0; if there are problems, it will print the logs and exit with status code 1.

sample error logs

2024-12-11T16:23:20.279723+08:00 ERROR risingwave_meta::controller::scale: Integrity check failed: Fragment 249088 has different upstream_fragment_ids from discovered: {} != {249089, 249092}
2024-12-11T16:23:20.279797+08:00 ERROR risingwave_meta::controller::scale: Integrity check failed: Fragment 246009 has different upstream_fragment_ids from discovered: {} != {223031}
2024-12-11T16:23:20.279828+08:00 ERROR risingwave_meta::controller::scale: Integrity check failed: Fragment 249084 has different upstream_fragment_ids from discovered: {} != {181025}
2024-12-11T16:23:20.279865+08:00 ERROR risingwave_meta::controller::scale: Integrity check failed: Fragment 258005 has different upstream_fragment_ids from discovered: {} != {181025}
...

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.