Warn on wrong Concatenate usage

I once again fell into the trap of using `Concatenate` inside its own square brackets and not as the first argument as it is intended, e.g. `Callable[[Concatenate[int, P]], None]` while it should be `Callable[Concatenate[int, P], None]`.
This results in some weird assignment errors later on that are hard to interpret:

> "Concatenate[int, (int)]" is not assignable to "int"

Instead (or in combination) there should be an error during the definition.

**Code or Screenshots**
Code sample in [pyright playground](https://pyright-play.net/?enableExperimentalFeatures=true&code=GYJw9gtgBALgngBwJYDsDmUkQWEMoDCAhgDYlEBGJApgDSFgoDGRM1KrdUACkSERADKCak3oBBFHACwAKDnwRhANoAqVdwC6UALyFS5KtWXKCjFmw5tlqGPS2b6AOUbVNcud108%2BA4aIAKACJuIIBKD1kAE2pgKGAwMACiAC5MFDsoCjTbMKgAWgA%2BKBcUajSAOirImLimAAtRAGsA4DSCGwzNMMrq%2BVkG5tbEsKA)

```python
from typing import Callable, Concatenate, ParamSpec

type C[**P] = Callable[[Concatenate[int, P]], None] # no error on misuse

P = ParamSpec("P")

def foo(a: int, b: int) -> None: ...

def check(f: C[int]): ...

check(foo) # "Concatenate[int, (int)]" is not assignable to "int"
```

**VS Code extension or command-line**
1.1.408

Start by reproducing the provided Python example in the linked pyright playground using version 1.1.408, then trace how Concatenate usage is validated during type definition and assignment checking. Done means the misuse produces a diagnostic at definition time, rather than only the later confusing assignment error.

Written by the indexing model from the issue text.