Parser: Don't search for Action View Tag Helpers recursively

[marcoroth]

This pull request fixes a bug in the parser analysis phase with action_view_helpers: true enabled where search_tag_helper_node would recursively traverse the entire Prism AST of an ERB expression, causing tag helpers nested inside another call's arguments or block body to be incorrectly detected and transformed as the top-level tag helper.

For example, the following template:

<% content_for :head, tag.meta(name: "viewport", content: "width=device-width, initial-scale=1") %>

Would incorrectly transform the ERBContentNode as if tag.meta were the outermost call. It now correctly produces the following using action_view_helpers: true:

@ DocumentNode (location: (1:0)-(2:0))
└── children: (2 items)
    ├── @ ERBContentNode (location: (1:0)-(1:99))
    │   ├── tag_opening: "<%" (location: (1:0)-(1:2))
    │   ├── content: " content_for :head, tag.meta(name: "viewport", content: "width=device-width, initial-scale=1") " (location: (1:2)-(1:97))
    │   ├── tag_closing: "%>" (location: (1:97)-(1:99))
    │   ├── parsed: true
    │   └── valid: true
    │
    └── @ HTMLTextNode (location: (1:99)-(2:0))
        └── content: "\n"

The fix stops recursion at any PM_CALL_NODE that doesn't match a known tag helper. A tag helper must be the outermost call in the ERB expression, not nested inside another call's arguments or block body.

Resolves #1423
Resolves #1429

[pkg-pr-new]

npx https://pkg.pr.new/@herb-tools/formatter@1431

npx https://pkg.pr.new/@herb-tools/language-server@1431

npx https://pkg.pr.new/@herb-tools/linter@1431

commit: 5dadfa1

[github-actions]

🌿 Interactive Playground and Documentation Preview

A preview deployment has been built for this pull request. Try out the changes live in the interactive playground:

• Playground Preview
• Documentation Preview
• Website Preview

---

_{🌱 Grown from commit 5dadfa1}

---

✅ Preview deployment has been cleaned up.