Overload type narrowing based on number of arguments instead of argument-type

Personne n'a encore pris cette issue.

With the following code:
```
---@overload fun(param1: "test", param2: string)
---@overload fun(param1: "test2", param2: number)
---@overload fun(param1: "test3", param2: boolean, param3: number)
local function test(...)
end

test("test", "string"); ---expected: good, actual: good
test("test2", 1); ---expected: good, actual: good
test("test3", true, 1); ---expected: good, actual: good

test("test", 1); ---expected: bad, actual: good
test("test2", "string"); ---expected: bad, actual: good

test("test", true, 2) ---expected: bad, actual: bad
test("test3", "string"); ---expected: bad, actual: bad
test("test3", "string", 1); ---expected: bad, actual: bad
test("test3", true); ---expected: bad, actual: bad
```

I get the following errors:

With these overloads I would of expected the type to be equivalent to this:
```
{
param1: "test"
param2: string
} | {
param1: "test2"
param2: number
} | {
param1: "test3"
param2: boolean
param3: number
}
```
However, it is actually equivalent to:
```
{
param1: "test" | "test2"
param2: string | number
} |
{
param1: "test3"
param2: boolean
param3: number
}
```

Commencez par reproduire l’exemple de surcharge dans l’issue et suivez le chemin de vérification des types du language server pour les appels de fonctions surchargées. Le correctif est complet lorsque les types des arguments affinent les surcharges aussi bien que le nombre d’arguments, en acceptant les trois appels valides et en rejetant les appels incompatibles indiqués.

Rédigé par le modèle d'indexation à partir du texte de l'issue.