*: support batch create/drop bindings from plan/sql digest

[time-and-fate]

What problem does this PR solve?

Issue Number: close #55343

What changed and how does it work?

• Parser
  • Introduce StringLitOrUserVariableList syntax and corresponding struct StringOrUserVar data type.
  • Change the input of "create from plan digest" and "drop for SQL digest" from stringLit to StringLitOrUserVariableList.
• Planner
  • Split struct SQLBindPlan into struct SQLBindPlan and struct SQLBindOpDetail, and make one SQLBindPlan able to contain multiple SQLBindOpDetail. (common_plans.go)
  • Add collectStrOrUserVarList() to translate []*ast.StringOrUserVar into []string. (planbuilder.go)
  • Extract constructSQLBindOPFromPlanDigest() from buildCreateBindPlanFromPlanDigest(). (planbuilder.go)
  • Make buildCreateBindPlanFromPlanDigest() and buildDropBindPlan() able to handle input from []*ast.StringOrUserVar, which means multiple digests. (planbuilder.go)
• Executor
  • Switch to use struct SQLBindOpDetail accordingly as stated above.
  • Switch to the new /bindinfo interface as stated below.
• /bindinfo
  • Input for CreateGlobalBinding(): binding Binding -> bindings []*Binding
  • Input for DropGlobalBinding(): sqlDigest string -> sqlDigests []string
  • Input for CreateSessionBinding(): binding Binding -> bindings []*Binding
  • Input for DropSessionBinding(): sqlDigest string -> sqlDigests []string

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

Attention: Patch coverage is 78.89610% with 65 lines in your changes missing coverage. Please review.

Project coverage is 74.6768%. Comparing base (6a34088) to head (7cb79d1).

❗ Current head 7cb79d1 differs from pull request most recent head 404ccdf

Please upload reports for the commit 404ccdf to get more accurate results.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #55315        +/-   ##
================================================
+ Coverage   72.9273%   74.6768%   +1.7495%     
================================================
  Files          1575       1575                
  Lines        440127     440566       +439     
================================================
+ Hits         320973     329001      +8028     
+ Misses        99454      91334      -8120     
- Partials      19700      20231       +531     

Flag	Coverage Δ
integration	49.3312% <57.4675%> (?)
unit	71.8199% <78.8961%> (-0.1635%)	⬇️

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

Components	Coverage Δ
dumpling	52.9567% <ø> (ø)
parser	∅ <ø> (∅)
br	52.4494% <ø> (+6.5908%)	⬆️

[easonn7]

/approve

[winoros]

/hold for two approve from planner

[time-and-fate]

/retest

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2024-08-12 08:13:39.2496647 +0000 UTC m=+169303.953134367: ☑️ agreed by qw4990.
• 2024-08-12 09:32:20.366478911 +0000 UTC m=+174025.069948570: ☑️ agreed by tangenta.

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

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

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 [qw4990,tangenta,winoros]
• pkg/bindinfo/OWNERS [qw4990,winoros]
• pkg/infoschema/OWNERS [tangenta]
• pkg/parser/OWNERS [easonn7,tangenta]
• pkg/planner/OWNERS [qw4990,winoros]

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

[time-and-fate]

/unhold