fix: reduct credentials in rw_catalog

[tabVersion]

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

What's changed and what's your intention?

as title

related #19689 & #19766

Checklist

• I have written necessary rustdoc comments.
• I have added necessary unit tests and integration tests.
• I have added test labels as necessary.
• I have added fuzzing tests or opened an issue to track them.
• My PR contains breaking changes.
• My PR changes performance-critical code, so I will run (micro) benchmarks and present the results.
• My PR contains critical fixes that are necessary to be merged into the latest release.

Documentation

• My PR needs documentation updates.

Release note

[fuyufjh]

Weakly -1. IMO, This is not something that a system table should do.

[fuyufjh]

Weakly -1. IMO, This is not something that a system table should do.

Just saying, for example, if we develop a rw_dump tool like pg_dump, it will fetch all information from system catalog. The system table is supposed to be a source of truth to be read for external tools.

---

I think we are able to mitigate the issue via proper privilge check #19722.

[tabVersion]

I think we are able to mitigate the issue via proper privilge check #19722.

+1 for this. Limiting the privilege to rw_catalog can prevent leaking.

Another motivation for the PR is the cloud team also don't want to display the credentials on the portal, there has to be a mosaic step.