planner: fix incorrectly using the schema for plan cache

[wjhuang2016]

What problem does this PR solve?

Issue Number: close #56733

Problem Summary:
If the table ID is changed for a given table name, the plan cache key is not updated.
For an insert statement, it may use the outdated schema, resulting in incorrect data or query results.

What changed and how does it work?

Make sure the tbl is updated in function planCachePreprocess() if tableByID doesn't return the table info.

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.

fix incorrectly using the schema for plan cache

[codecov]

Codecov Report

Attention: Patch coverage is 50.00000% with 3 lines in your changes missing coverage. Please review.

Project coverage is 74.7843%. Comparing base (d021648) to head (c965705).
Report is 27 commits behind head on master.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #57964        +/-   ##
================================================
+ Coverage   73.1421%   74.7843%   +1.6422%     
================================================
  Files          1671       1719        +48     
  Lines        460703     475114     +14411     
================================================
+ Hits         336968     355311     +18343     
+ Misses       102998      97476      -5522     
- Partials      20737      22327      +1590     

Flag	Coverage Δ
integration	49.0871% <50.0000%> (?)
unit	72.2772% <50.0000%> (+0.0027%)	⬆️

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

Components	Coverage Δ
dumpling	52.6910% <ø> (ø)
parser	∅ <ø> (∅)
br	61.6530% <ø> (+15.6636%)	⬆️

[wjhuang2016]

/retest

[zimulala]

LGTM

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2024-12-06 09:41:27.704097415 +0000 UTC m=+1407075.323751936: ☑️ agreed by tangenta.
• 2024-12-09 07:25:48.182836306 +0000 UTC m=+250538.271638849: ☑️ agreed by zimulala.

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: qw4990, tangenta, zimulala

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:

• pkg/ddl/OWNERS [tangenta]
• pkg/planner/OWNERS [qw4990]

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

[wjhuang2016]

/run-cherry-picker release-8.5

[ti-chi-bot]

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

[ti-chi-bot]

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

[ti-chi-bot]

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

[ti-chi-bot]

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

[ti-chi-bot]

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