IndexLookUpExecutor use too many memory and can't be killed.

[wshwsh12]

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

During the index look up range construction, the memory tracker and killsignal were not properly passed into the function, causing memory to be untraceable.

2. What did you expect to see? (Required)

3. What did you see instead (Required)

4. What is your TiDB version? (Required)

master, v8.3.0

[wshwsh12]

Reproduced Step:

1. Build data 8000000 rows.
   create table t2(a int, b int, c int, index idx(b)) partition by hash(a) partitions 100;
   insert into values from 1-8000000
2. Run sql. desc analyze select /*+ inl_hash_join(t1) */ * from t2 t1 join t2 t2 on t1.b=t2.b; and wait 60s.
3. Get heap profile.

4. Cancel the sql and show the slow log. The sql only trace 50MB.