potential leak problem of memtracker

[XuHuaiyu]

Enhancement

From #54005, we have identified a potential issue where some operator's memtracker objects might not be detached properly, leading to memory leaks. When these operators act as the inner child of an apply operator, they are repeatedly opened and closed, causing the leaked memTracker and Action objects to remain referenced and unreclaimed. This results in uncontrolled memory accumulation.

We need to construct a set of tests to observe different operators when they act as the inner child of an apply operator. By capturing heap profiles, we aim to determine if there are any memtracker or action leaks.

[XuHuaiyu]

It is important to note that we cannot detach the operator's memTracker in the operator.Close method, as this would prevent explain analyze from retrieving the memory consumption value associated with the operator. Instead, we should perform the detachment in the operator.Open method by calling operator.memTracker.Reset() when the operator.memTracker is not null.