infoschema: support query partition_id from infoschema.partitions (#22240)

[ti-srebot]

cherry-pick #22240 to release-4.0
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/22489

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

git push git@github.com:ti-srebot/tidb.git pr/22489:release-4.0-b24095d909e7

---

Signed-off-by: lysu sulifx@gmail.com

What problem does this PR solve?

Problem Summary:

current we has no easy way to get partition ids for a table, but sometime we need it to help diagnose

What is changed and how it works?

What's Changed, How it Works:

add TIDB_PARTITION_ID to information_schema.partitions

Related changes

• Need to cherry-pick to the release branch 4.0/5.0.rc to help diagnose in oncall

Check List

Tests

• Unit test

Side effects

• n/a

Release note

• support query partition_id from infoschema.partitions

---

This change is 

[ti-srebot]

/run-all-tests

[ti-srebot]

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

[ti-srebot]

@jackysp, @qw4990, @winoros, PTAL.

[jackysp]

LGTM

[ti-chi-bot]

@jackysp: Please use /LGTM instead of LGTM when you want to approve the pull request by comment.
If you use the GitHub review feature, please approve the PR directly, the comment will not take effect in the GitHub review feature.
If you have any qustions please refer to lgtm command help or lgtm plugin design.

If you have approved this PR, please ignore this reply. This reply is being used as a temporary reply during the migration of the new bot and will be removed on April 1.

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.

[jackysp]

/lgtm

[ti-srebot]

@jackysp, @qw4990, @winoros, PTAL.

[ti-srebot]

@jackysp, @qw4990, @winoros, PTAL.

[qw4990]

/LGTM

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has been approved by:

• jackysp
• qw4990

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 writing /lgtm in a comment.
Reviewer can cancel approval by writing /lgtm cancel in a comment.

[lysu]

/merge

[ti-chi-bot]

@lysu: It seems you want to merge this PR, I will help you trigger all the tests:

/run-all-tests

You only need to trigger /merge once, and 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.

If you have any questions about the PR merge process, please refer to pr process.

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]

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

Commit hash: 78f19b1

[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

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.