fix(interactive): fix memory leaks in complex data structures and support generic tuple

[liulx20]

Fixes

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 58.78%. Comparing base (383a1e0) to head (06202cc).
Report is 2 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #4468   +/-   ##
=======================================
  Coverage   58.78%   58.78%           
=======================================
  Files          12       12           
  Lines         592      592           
=======================================
  Hits          348      348           
  Misses        244      244           

---

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 383a1e0...06202cc. Read the comment docs.

[github-actions]

Please check the preview of the documentation changes at
https://f92f84ce.graphscope-docs-preview.pages.dev

[zhanglei1949]

Is the capture&ctx safe? Since ctx has already been applied with std::move in .Execute.

[liulx20]

I think it's ok here, as described in this. The object being moved is put into a 'valid but unspecified state.' This means that after an object is moved from, it can still be accessed safely, but you should not make any assumptions about its value or state. In this case, we are not accessing the content of context when an error occurs.