Fix Unknown and Any variables being coloured as Unbound

[ValdezFOmar]

Fixes #180

[github-actions]

According to mypy_primer, this change doesn't affect type check results on a corpus of open source code. ✅

[ValdezFOmar]

I noticed that Any is being coloured as a variable instead of a type and that is already an open issue (#150). Looking at how is defined in typeshed makes sense that it would be coloured this way, but is really odd that they decided to do this in the first place.

basedpyright/packages/pyright-internal/typeshed-fallback/stdlib/typing.pyi

Line 138 in b1ebff9

Any = object()

[DetachHead]

I noticed that Any is being coloured as a variable instead of a type and that is already an open issue (#150). Looking at how is defined in typeshed makes sense that it would be coloured this way, but is really odd that they decided to do is in the first place.

basedpyright/packages/pyright-internal/typeshed-fallback/stdlib/typing.pyi

Line 138 in b1ebff9

Any = object()

yeah that's really weird. @KotlinIsland any idea what's up with that? should we just change it to _SpecialForm to match the others?

[KotlinIsland]

Yeah, it's bizarre how they wrote typing.pyi, we could try changing it to _SpecialForm and see if it breaks anything.

Surprisingly, it looks like it's already special-cased to some extent:

from typing import Any

reveal_type(Any)  # Type of "Any" is "Any"

It will actually depend on the version of python, as it's not a _SpecialForm any more, it's a _AnyMeta now.

[KotlinIsland]

• Fix the stubs for Any #236