[Rust APIView] Result is rendered without resolving azure_core::Result import

**Bad code snippet**
```rust
pub fn new(tenant_id: &str, client_id: String, secret: Secret, options: Option) -> Result> {}
```

**What should happen**
APIView should resolve the imported Rust result type and render it as `azure_core::Result`, since `Result` in this context is an alias/import of `azure_core::Result` rather than the unqualified standard/library type. The current rendering makes it look unresolved or ambiguous.

**Good code snippet**
```rust
pub fn new(tenant_id: &str, client_id: String, secret: Secret, options: Option) -> azure_core::Result> {}
```

Start in the APIView Rust parsing and import-resolution path, using the bad and good code snippets in this issue as the reproduction. Trace how the imported Result type is rendered, then verify that the output qualifies it as azure_core::Result rather than leaving it unqualified or ambiguous.

Written by the indexing model from the issue text.