executor, privilege: require CONFIG or Process privilege for is.cluster_*

[mjonss]

What problem does this PR solve?

Issue Number: close #26121,#26122,#26123,#26124,#26126

Problem Summary:
The information_schema.cluster_* tables should require the CONFIG or Process privilege. This is consistent with the behavior change in #25379 which requires CONFIG for SHOW CONFIG.

It makes sense to cherry pick to 5.1, but not 5.0; because the behavior in 5.0 was not established yet, and SHOW CONFIG still requires no privileges.

What is changed and how it works?

What's Changed:

Reading from the table information_schema.cluster_hardware now requires the CONFIG privilege.
Reading from the table information_schema.cluster_{info,load,systeminfo,log} now requires the CONFIG privilege.

Check List

Tests

• Unit test

Side effects

• Breaking backward compatibility (for security)

Release note

• Reading from the table information_schema.cluster_hardware now requires the CONFIG privilege.
• Reading from the table information_schema.cluster_info now requires the Process privilege.
• Reading from the table information_schema.cluster_load now requires the Process privilege.
• Reading from the table information_schema.cluster_systeminfo now requires the Process privilege.
• Reading from the table information_schema.cluster_log now requires the Process privilege.

[mjonss]

Current patch breaks the telemetry test, due to lack of Process privileges for i_s.cluster_info table.

[AilinKid]

LGTM

[ti-chi-bot]

@morgo: Thanks for your review. The bot only counts approvals from reviewers and higher roles in list, but you're still welcome to leave your comments.

In response to this:

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository.

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has been approved by:

• AilinKid
• morgo

To complete the pull request process, please ask the reviewers in the list to review by filling /cc @reviewer in the comment.
After your PR has acquired the required number of LGTMs, you can assign this pull request to the committer in the list by filling /assign @committer in the comment to help you merge this pull request.

The full list of commands accepted by this bot can be found here.

Reviewer can indicate their review by submitting an approval review.
Reviewer can cancel approval by submitting a request changes review.

[morgo]

/merge

[ti-chi-bot]

This pull request has been accepted and is ready to merge.

Commit hash: b1b06e9

[morgo]

/run-unit-test

[ti-srebot]

cherry pick to release-5.1 in PR #26297