distsql: use a more accurate type of the context of distsql

[YangKeao]

What problem does this PR solve?

Issue Number: close #51617

Problem Summary:

The distsql only needs a subset of the whole session variables and context, so we can use a more accurate type to represent it. This refactor will help us to clone it in the future.

What changed and how does it work?

1. Give a struct DistSQLContext, which contains all information needed by the session.
2. Add a cache on the StmtCtx, because the cache should be invalidated after each execution.
3. Remove the dependency of stmtctx (and session, maybe) from distsql.

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.
    It should be covered by existing tests. Some tests also need to be modified.

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

None

[ti-chi-bot]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[tiprow]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[YangKeao]

/retest

[YangKeao]

/retest

[codecov]

Codecov Report

Merging #51618 (c201821) into master (db0d581) will decrease coverage by 0.0186%.
Report is 2 commits behind head on master.
The diff coverage is 92.2509%.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #51618        +/-   ##
================================================
- Coverage   70.7391%   70.7205%   -0.0186%     
================================================
  Files          1491       1563        +72     
  Lines        440448     460337     +19889     
================================================
+ Hits         311569     325553     +13984     
- Misses       109378     114159      +4781     
- Partials      19501      20625      +1124     

Flag	Coverage Δ
integration	47.5936% <83.0258%> (?)
unit	70.4693% <88.5608%> (-0.0948%)	⬇️

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

Components	Coverage Δ
dumpling	53.9957% <ø> (ø)
parser	∅ <ø> (∅)
br	51.4973% <ø> (+5.6847%)	⬆️

[YangKeao]

/retest

[YangKeao]

/retest

[YangKeao]

/retest

[YangKeao]

/retest

[YangKeao]

/retest

[YangKeao]

/retest

[YangKeao]

/retest

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2024-03-18 04:05:45.861737822 +0000 UTC m=+1263172.883984208: ☑️ agreed by lcwangchao.
• 2024-03-26 06:39:05.530649646 +0000 UTC m=+1963572.552896033: ☑️ agreed by zimulala.

[tiprow]

@YangKeao: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
fast_test_tiprow	c201821	link	true	/test fast_test_tiprow

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: lcwangchao, XuHuaiyu, 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:

• OWNERS [XuHuaiyu,lcwangchao,zimulala]
• pkg/ddl/OWNERS [zimulala]
• pkg/distsql/OWNERS [XuHuaiyu]

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