New-types seem to have an under-specified callable signature of `(...) -> Any` on 1.1.402

**Describe the bug**

Types created with `NewType` seem to have a callable signature of `(...) -> Any` now instead of `(old_type) -> new_type`.

**Code or Screenshots**

```python
from __future__ import annotations

from collections.abc import Callable
from typing import NewType, Protocol

NewInt = NewType("NewInt", int)

class FP(Protocol):
def __call__(self, /) -> None: ...

fp: FP = NewInt # Expected to be reported as incompatible, but NOT.

def call[**P, T](f: Callable[P, T], *args: P.args, **kwargs: P.kwargs) -> T: ...
reveal_type(call(NewInt, 0)) # Expected to have a result type of `NewInt`, but got `Any` instead.
call(NewInt) # Expected to be reported as invalid call, but NOT.
```

**VS Code extension or command-line**

This behavior is new since 1.1.402.

Run the provided Python reproducer against Pyright 1.1.402 and compare its diagnostics and revealed type with the expected results. Trace the NewType callable-signature handling; done means incompatible assignments and missing arguments are reported, and the generic call reveals NewInt rather than Any.

Written by the indexing model from the issue text.