feat: add rw_rate_limit system catalog

[xxchan]

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

What's changed and what's your intention?

It's not easy to know what jobs are rate limited, so add this.

I want to avoid iterating over all fragments, so I introduced a new fragment flag for FsFetch. This means rw_rate_limit won't show fs fragments created before this PR, and I think it's acceptable.

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 #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.

[xxchan]

• #19466 👈 (View in Graphite)
• #19445
• #19443
• main

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

[xxchan]

Oops. Seems this system catalog is not isolated between databases 🤔

Some catalogs support this, but some don't: e.g,

• rw_tables is isolated
• rw_fragments is not

[yezizp2012]

Oops. Seems this system catalog is not isolated between databases 🤔

Some catalogs support this, but some don't: e.g,

• rw_tables is isolated
• rw_fragments is not

System catalogs about metadata of the streaming job are all not isolated between databases. They are used solely for debugging.

[xxchan]

Yes, I was also a little hesitant to add isolation which might hurt debugging. 🤪

[xxchan]

Merge activity

• Nov 20, 3:57 PM GMT+8: A user started a stack merge that includes this pull request via Graphite.
• Nov 20, 3:58 PM GMT+8: Graphite couldn't merge this pull request because a downstack PR #19443 failed to merge.
• Nov 20, 7:42 PM GMT+8: Graphite rebased this pull request after merging its parent, because this pull request is set to merge when ready.
• Nov 20, 8:35 PM GMT+8: Graphite couldn't merge this PR because it failed for an unknown reason (This repository has GitHub's merge queue enabled, which is currently incompatible with Graphite).
• Nov 20, 8:36 PM GMT+8: Graphite couldn't merge this PR because it failed for an unknown reason (This repository has GitHub's merge queue enabled, which is currently incompatible with Graphite).