expression: refactor cache implement for regexp_like/regexp_instr/regexp_replace

[lcwangchao]

What problem does this PR solve?

Issue Number: close #49641

Problem Summary:

After #49584 , we have refactored the implement for function regexp_substr. This PR refactors other regexp functions.

What changed and how does it work?

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
• No need to test

  • I checked and no code files have been changed.

Side effects

• Performance regression: Consumes more CPU
• Performance regression: Consumes more Memory
• Breaking backward compatibility

Documentation

• Affects user behaviors
• Contains syntax changes
• Contains variable changes
• Contains experimental features
• Changes MySQL compatibility

Release note

Please refer to Release Notes Language Style Guide to write a quality release note.

None

[codecov]

Codecov Report

Merging #49642 (05b1a57) into master (8219934) will increase coverage by 0.4779%.
Report is 10 commits behind head on master.
The diff coverage is 55.8823%.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #49642        +/-   ##
================================================
+ Coverage   70.9796%   71.4575%   +0.4779%     
================================================
  Files          1368       1423        +55     
  Lines        398699     417368     +18669     
================================================
+ Hits         282995     298241     +15246     
- Misses        95933     100300      +4367     
+ Partials      19771      18827       -944     

Flag	Coverage Δ
integration	43.7198% <55.8823%> (?)
unit	70.9809% <ø> (+0.0013%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Components	Coverage Δ
dumpling	53.9663% <ø> (ø)
parser	∅ <ø> (∅)
br	47.3109% <ø> (-5.5717%)	⬇️

[lcwangchao]

/test tiprow_fast_test

[ti-chi-bot]

@lcwangchao: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

• /test build
• /test check-dev
• /test check-dev2
• /test mysql-test
• /test pull-integration-ddl-test
• /test pull-mysql-client-test
• /test unit-test

The following commands are available to trigger optional jobs:

• /test canary-notify-when-compatibility-sections-changed
• /test pingcap/tidb/canary_ghpr_unit_test
• /test pull-br-integration-test
• /test pull-common-test
• /test pull-e2e-test
• /test pull-integration-common-test
• /test pull-integration-copr-test
• /test pull-integration-jdbc-test
• /test pull-integration-mysql-test
• /test pull-integration-nodejs-test
• /test pull-lightning-integration-test
• /test pull-sqllogic-test
• /test pull-tiflash-test

Use /test all to run the following jobs that were automatically triggered:

• pingcap/tidb/ghpr_build
• pingcap/tidb/ghpr_check
• pingcap/tidb/ghpr_check2
• pingcap/tidb/ghpr_mysql_test
• pingcap/tidb/ghpr_unit_test
• pingcap/tidb/pull_integration_ddl_test
• pingcap/tidb/pull_mysql_client_test

In response to this:

/test tiprow_fast_test

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.

[xzhangxian1008]

LGTM

[ti-chi-bot]

@xzhangxian1008: adding LGTM is restricted to approvers and reviewers in OWNERS files.

In response to this:

LGTM

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.

[YangKeao]

LGTM

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: XuHuaiyu, xzhangxian1008, YangKeao

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 [XuHuaiyu,YangKeao]
• pkg/expression/OWNERS [XuHuaiyu]

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]

[LGTM Timeline notifier]

Timeline:

• 2023-12-21 07:06:23.092782177 +0000 UTC m=+1117474.130009104: ☑️ agreed by YangKeao.
• 2023-12-21 07:41:24.565759935 +0000 UTC m=+1119575.602986862: ☑️ agreed by XuHuaiyu.