executor, privilege: require CONFIG or Process privilege for is.cluster_* (#26220)

[ti-srebot]

cherry-pick #26220 to release-5.1
You can switch your code base to this Pull Request by using git-extras:

# In tidb repo:
git pr https://github.com/pingcap/tidb/pull/26297

After apply modifications, you can push your change to this PR via:

git push git@github.com:ti-srebot/tidb.git pr/26297:release-5.1-946b3841e7f0

---

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.

[ti-srebot]

/run-all-tests

[ti-srebot]

@mjonss you're already a collaborator in bot's repo.

[AilinKid]

/LGTM

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has been approved by:

• AilinKid
• djshow832

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.

[AilinKid]

/merge

[ti-chi-bot]

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

Commit hash: 16da8c9

[ti-chi-bot]

@ti-srebot: Your PR was out of date, I have automatically updated it for you.

At the same time I will also trigger all tests for you:

/run-all-tests

If the CI test fails, you just re-trigger the test that failed and the bot will merge the PR for you after the CI passes.

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.