fix(frontend): add stream_job_status to TableCatalog

[kwannoel]

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

What's changed and what's your intention?

To make sure TableCatalog and Table are isomorphic.

Also required by ALTER MV for rate limit on creating mv. See: #16399

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.

[chenzl25]

IIRC, only the table with created status would be notified to the frontend node. In which case, do we need to handle creating mv in the frontend node?

[kwannoel]

IIRC, only the table with created status would be notified to the frontend node. In which case, do we need to handle creating mv in the frontend node?

Yes, in a separate PR I will add that logic. Without the creating mv catalog in the frontend, we can't alter its rate limit, since we don't have sufficient info about its schema, database. Those info are in its TableCatalog.

[chenzl25]

LGTM