executor: add memory tracker for memtableRetriever (#51455)

[ti-chi-bot]

This is an automated cherry-pick of #51455

What problem does this PR solve?

Issue Number: close #51456
related #51260

Problem Summary:

What changed and how does it work?

Add memory tracker for memtableRetriever

Check List

Tests

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

Test Case: 50k tables, each table contains 10 columns.

Test1: Testing 'explain analyze' to accurately display memory usage.

tidb> desc analyze select * from INFORMATION_SCHEMA.tables;
+----------------+----------+---------+------+---------------+-------------------------------------+---------------+---------+------+
| id             | estRows  | actRows | task | access object | execution info                      | operator info | memory  | disk |
+----------------+----------+---------+------+---------------+-------------------------------------+---------------+---------+------+
| MemTableScan_4 | 10000.00 | 50816   | root | table:TABLES  | time:115.1ms, loops:51, RU:0.000000 |               | 91.3 MB | N/A  |
+----------------+----------+---------+------+---------------+-------------------------------------+---------------+---------+------+
1 row in set (0.116 sec)

Test2: Testing mem-quota to successfully cancel SQL queries exceeding the threshold.

tidb> set tidb_mem_quota_query = 80 << 20;
Query OK, 0 rows affected (0.001 sec)

tidb> desc analyze select * from INFORMATION_SCHEMA.tables;
ERROR 8175 (HY000): Your query has been cancelled due to exceeding the allowed memory limit for a single SQL query. Please try narrowing your query scope or increase the tidb_mem_quota_query limit and try again.[conn=463470598]

• 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

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: YangKeao, ywqzzy

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 [YangKeao]

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:

• 2024-04-23 02:33:01.783723239 +0000 UTC m=+54738.523626143: ☑️ agreed by ywqzzy.
• 2024-04-23 02:33:36.233134058 +0000 UTC m=+54772.973036969: ☑️ agreed by YangKeao.

[codecov]

Codecov Report

❗ No coverage uploaded for pull request base (release-7.1@3917c31). Click here to learn what that means.
The diff coverage is 100.0000%.

Additional details and impacted files

@@               Coverage Diff                @@
##             release-7.1     #52823   +/-   ##
================================================
  Coverage               ?   73.4624%           
================================================
  Files                  ?       1211           
  Lines                  ?     380111           
  Branches               ?          0           
================================================
  Hits                   ?     279239           
  Misses                 ?      83062           
  Partials               ?      17810