fix(CORE-4563): Fix dispose infinite recursion

[iancamp]

While updating DAG to call dispose more, an infinite recursion bug was uncovered in nools.

The problem is that the graph nools builds can have cyclic nodes (A -> B -> ... -> A) so when it traversed the nodes during disposal it would get caught in infinite recursion of going through the same path over and over again. By marking nodes as visited we can signal that that node should not be traversed further because we've already visited it.

I also had cursor whip up some more exhaustive tests

(blocks https://github.com/immuta/bodata/pull/22057)

JIRA Ticket Link: https://immuta.atlassian.net/browse/CORE-4563

---

Note

Medium Risk
Touches core rete network disposal logic by adding cycle detection and expanding memory clearing across multiple node types; bugs here could cause leaks or incorrect cleanup but is covered by extensive new tests.

Overview
Fixes session.dispose() traversal to be cycle-safe by threading a shared visited map through RootNode/TypeNode and all Node/BetaNode dispose propagation, preventing infinite recursion on cyclic or shared graphs.

Extends disposal to clear additional per-node state (FromNode/FromNotNode fromMemory, NotNode leftTupleMemory) and removes redundant dispose overrides on adapter nodes. Adds a comprehensive regression test suite validating that beta/tuple memories, agenda state, and working memory are fully cleared and that dispose is idempotent.

Modernizes project tooling by migrating CI from Travis to GitHub Actions, adding mise Node pinning/lock, generating package-lock.json, and bumping the declared Node engine requirement to >= 22 (including README badge update).

^{Reviewed by Cursor Bugbot for commit 0b272b7. Bugbot is set up for automated code reviews on this repo. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{Reviewed by Cursor Bugbot for commit 59670a5. Configure here.}