fix Render callable protocols in hover as the signature of __call__ rather than by name #2832

[asukaminato0721]

Summary

Fixes #2832

coercing the hovered type to its callable form only when the cursor is actually on the callee.

preserves the existing constructor special case and avoids changing plain attribute hovers.

Test Plan

add test

[Copilot]

Pull request overview

Fixes hover rendering for callable protocol attributes so that, when hovering the callee in a call expression, the hover displays the __call__ signature (instead of showing an attribute named __call__). This aligns hover behavior with how callable instances are already rendered and avoids affecting non-call-site (plain attribute) hovers.

Changes:

• Only coerce the hovered type to a callable when the hover position is actually within the callee range of a call expression.
• Preserve the existing “constructor call” special-case behavior for hover display.
• Add a regression test covering callable protocol attributes used as callees.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
pyrefly/lib/lsp/wasm/hover.rs	Gates callable coercion behind “hover is on callee” so call-site hovers show __call__ signatures without impacting other hovers.
pyrefly/lib/test/lsp/hover.rs	Adds a regression test ensuring callable protocol attributes render the __call__ signature on hover at the call site.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[github-actions]

According to mypy_primer, this change doesn't affect type check results on a corpus of open source code. ✅