fix: prevent unique stack traces explosion in mem profile

[cheb0]

Description

Currently, fixing it only for tree folding. It's harder to fix nodeOr since using a single call site reduces performance of OR queries. However, currently most allocs (LID block reads) happen when deep trees are created (we have eager LID cursors), so I assume the fix makes sense. nodeOr will be fixed with unrolled nodes and batched execution (partially).

---

• I have read and followed all requirements in CONTRIBUTING.md;
• I used LLM/AI assistance to make this pull request;

[github-actions]

🔴 Performance Degradation

Some benchmarks have degraded compared to the previous run.
Click on Show table button to see full list of degraded benchmarks.

Show table

Name	Previous	Current	Ratio	Verdict
Indexer-4	42fb1c	e9e0a4
	572784732.00 B/op	769851024.00 B/op	1.34	🔴

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 70.41%. Comparing base (1bcd504) to head (de49d73).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #464      +/-   ##
==========================================
- Coverage   70.42%   70.41%   -0.01%     
==========================================
  Files         232      232              
  Lines       18371    18371              
==========================================
- Hits        12937    12936       -1     
- Misses       4456     4458       +2     
+ Partials      978      977       -1     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.