Intellisense: deprioritise native function methods

Nessuno ha ancora preso questa issue.

### 🔍 Search Terms

native methods apply bind deprioritise autocomplete

### ✅ Viability Checklist

- [x] This wouldn't be a breaking change in existing TypeScript/JavaScript code
- [x] This wouldn't change the runtime behavior of existing JavaScript code
- [x] This could be implemented without emitting different JS based on the types of the expressions
- [x] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
- [x] This isn't a request to add a new utility type: https://github.com/microsoft/TypeScript/wiki/No-New-Utility-Types
- [x] This feature would agree with the rest of our Design Goals: https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals

### ⭐ Suggestion

In autocomplete on a function, it would be great if TypeScript could prioritise extra methods/properties over the native ones.

### 📃 Motivating Example

Bun has some APIs that exist on a function, for example `Bun.inspect()` and also `Bun.inspect.table`. When typing `Bun.inspect.` the first few suggestions are more likely not as useful as the extra properties

Here I would have preferred for `.custom` and `.table` to be first in the list:


### 💻 Use Cases

1. What do you want to use this for?: Would make it easier for the developer to discover often more useful methods and properties
2. What shortcomings exist with current approaches?: Extra methods/props are more difficult to see
4. What workarounds are you using in the meantime?: N/A

I would be very happy to help implement this, with some guidance as to roughly where I should look to implement it! Cheers.