fix doesn't understand usage of inline Annotated function parameters #2531

[asukaminato0721]

Summary

Fixes #2531

teaching hover/definition lookup to recover imported Annotated metadata symbols even when the use site has no type trace.

Attribute definition lookup now falls back to the exact base identifier when utils.

Name inside Annotated[...] lacks a trace, and hover now reuses the resolved definition to recover a displayable type instead of returning None.

Test Plan

add test

[Copilot]

Pull request overview

This PR fixes a Pyrefly LSP hover gap where symbols used inside inline typing.Annotated[...] metadata (and qualified type aliases used in parameter annotations) could fail to produce hover information due to missing type traces.

Changes:

• Add LSP hover regression tests covering qualified type aliases in annotations and imported Annotated metadata symbols.
• Improve attribute go-to-definition by recovering an attribute base type from the identifier when no type trace exists (notably for Annotated[..., utils.Name] cases).
• Improve hover fallback to derive the hovered type from the resolved definition when the use site lacks a type trace.

Reviewed changes

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

File	Description
pyrefly/lib/test/lsp/hover.rs	Adds regression tests for hovering qualified type aliases and imported Annotated metadata symbols.
pyrefly/lib/state/lsp.rs	Makes attribute definition lookup resilient to missing type traces by recovering the base type from the identifier at the base range.
pyrefly/lib/lsp/wasm/hover.rs	Adds a hover fallback path to compute the hovered type from the resolved definition when the use site has no type trace.

---

💡 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. ✅