Analysis: Rename PartialCallerIndex to RenderGraph and answer both directions

[marcoroth]

This pull request lets a rule ask what a render call hands back, which is what #2100 needs.

Today a rule can ask what encloses a partial. ancestorVerdict walks up from a partial through everything that renders it and answers always, never, mixed or unknown.

But, there was no way to ask the same question downwards, so this reports an offense it should not:

_panel.html.erb:

<details>
  <%= render "shared/summary" %>
  <p>Body</p>
</details>

_summary.html.erb:

<summary>More</summary>

The index already held both ends of every edge. callSites is keyed by callee, and each site records its caller, so the render relationships were all there. Only the queries were direction-specific.

What was missing is a property of the node to answer what a template puts at its own top level. Each template now records its TemplateRoots, the tags at its root, split into unconditional and conditional, along with the renders sitting at root position, resolved to files while the builder still has the partial index in hand.

That is why the class is renamed. PartialCallerIndex described one direction of something that now answers both.

[pkg-pr-new]

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

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

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

commit: 73deedb

[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 73deedb}

---

✅ Preview deployment has been cleaned up.