Typings do not catch mistyped fetcher arguments

# Bug report

```
// Should complain about wrong fetcher argument type being an array but expecting a string
useSWR("test", ([id]:[string]) => {})

// Should complain about fetcher argument must be an array
useSWR(["test"], (id) => {})
```

## Expected Behavior

Is this a limitation of TS or of the SWR typings?


SWR 2.3.4