Playground typing issue

### 🔎 Search Terms

TypeScript Playground error when attempting to import something from `@octokit/core/types`

### 🕗 Version & Regression Information

Seems irrelavent to TS version

### ⏯ Playground Link

https://www.typescriptlang.org/play/?#code/JYWwDg9gTgLgBAKjgQwM5wPIGMYQNbAwAqAnmAKboBmUEIcA5AAIQ76ED0W05HMZlBgCghoSLDgBvTGwLwAvnBp1GrXHIYBuEdwB2qeAHNCACwCuAIzgBeOLvIB3GesIAKAJTah5AB7j4egbO7MQCqF6+-nD8FMFypLG2MeQQVHDGMOYW2kA

### 💻 Code

```ts
import * as OctokitTypes from '@octokit/core/types';
```

### 🙁 Actual behavior

**Behavior 1**:

Type of the following variable is recognized as `any`:
```ts
import { Octokit } from 'octokit';
export type T = typeof Octokit;
```

**Behavior 2**:

Type of the following variable is recognized as `any`;
```ts
import * as OctokitTypes from '@octokit/core/types';
export const OctokitTypes;
```

**Behavior 3**: _Even stranger behavior_

In the following code snippet:
```ts
import * as OctokitTypes from '@octokit/core/types';
```

1. Remove any character from package name `@octokit/core/types` (e.g. `@octokit/core/type`), TS error occured, which is expected

2. Re-add the removed character, TS error remained, which is very weird

Apparently there is some problem with the language server, as the package name has been changed to `*/types`, but it still reports error of `*/type`

### 🙂 Expected behavior

N/A

### Additional information about the issue

_No response_

Start by reproducing the three behaviors in the linked TypeScript Playground, focusing on the @octokit/core/types import and the stale diagnostic after editing the package name. Trace the relevant module-resolution or language-server behavior; done means the valid import is resolved with its actual types and diagnostics update after the edit.

Written by the indexing model from the issue text.