Broken property suggestions due to a successfully contextually typed function

还没有人认领这个 Issue。

```ts
declare function makeRequest<
QueryParam
>(
getFn: (client: { prop: number }) => QueryParam,
params: NoInfer,
): void;

// Hovering over `makeRequest` shows that `QueryParam` is inferred as `unknown` and `params` is obstensibly typed as `unknown` which is incongruous with this call is an error.
makeRequest(
(client) => client,
// Using autocomplete here suggests globals, not `prop` like it should.
{},
// ^ Argument of type '{}' is not assignable to parameter of type '{ prop: number; }'.
);

makeRequest(
(client: { prop: number }) => client,
// Using autocomplete here now suggests keys.
{},
);
```

Sub-part of https://github.com/microsoft/TypeScript/issues/46916#issuecomment-2759515773 with parts pointed out with https://github.com/microsoft/TypeScript/issues/46916#issuecomment-2760441648

See @Andarist's analysis at https://github.com/microsoft/TypeScript/issues/46916#issuecomment-2760441648

从 issue 中的最小 TypeScript 复现开始，并阅读 issue #46916 及其评论中链接的分析。跟踪泛型函数的上下文类型推断和类型推断过程，然后验证 QueryParam 是从 callback 推断出来的，并确认 params 的自动补全会在没有显式 callback 注解的情况下提供 prop。

由索引模型根据 Issue 内容生成。