remove JSON_REPLACE from supported expressions for pushdown to TiKV

[Oreoxmt]

What is changed, added or deleted? (Required)

TiDB v4.x and later versions do not support pushing down JSON_REPLACE to TiKV

Which TiDB version(s) do your changes apply to? (Required)

Tips for choosing the affected version(s):

By default, CHOOSE MASTER ONLY so your changes will be applied to the next TiDB major or minor releases. If your PR involves a product feature behavior change or a compatibility change, CHOOSE THE AFFECTED RELEASE BRANCH(ES) AND MASTER.

For details, see tips for choosing the affected versions (in Chinese).

• master (the latest development version)
• v8.2 (TiDB 8.2 versions)
• v8.1 (TiDB 8.1 versions)
• v8.0 (TiDB 8.0 versions)
• v7.6 (TiDB 7.6 versions)
• v7.5 (TiDB 7.5 versions)
• v7.1 (TiDB 7.1 versions)
• v6.5 (TiDB 6.5 versions)
• v6.1 (TiDB 6.1 versions)
• v5.4 (TiDB 5.4 versions)
• v5.3 (TiDB 5.3 versions)
• v5.2 (TiDB 5.2 versions)
• v5.1 (TiDB 5.1 versions)

What is the related PR or file link(s)?

• This PR is translated from: remove JSON_REPLACE from supported expressions for pushdown to TiKV docs-cn#17714
• Other reference link(s): expression: fully open CAST push-down switcher tidb#14672

Do your changes match any of the following descriptions?

• Delete files
• Change aliases
• Need modification after applied to another branch
• Might cause conflicts after applied to another branch

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2024-06-18 05:53:37.031157409 +0000 UTC m=+94143.516646249: ☑️ agreed by hfxsd.

[ti-chi-bot]

@joey-yez: adding LGTM is restricted to approvers and reviewers in OWNERS files.

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 kubernetes/test-infra repository.

[Oreoxmt]

/approve

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Oreoxmt

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [Oreoxmt]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-6.5: #17923.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-7.1: #17924.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-8.0: #17926.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-5.3: #17927.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-5.4: #17928.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-6.1: #17929.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-5.2: #17930.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-7.5: #17931.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-5.1: #17940.