[Bug]: Incorrect overload handling for Any

What happened?

Since typing.Any matches literally anything, for @overload that start with special cases these are always picked in untyped code. Instead, @overload should prefer the most generic, conservative case.

This is related to and got my attention by the pandas concat type hints bug that causes Any -> ??? paths to select None -> Never overloads.

Minimal Reproducible Example

# Type test
# MyPy "correctly" reports the unused type ignore

async def test_filter_any(aitr: "AsyncIterator[int | None]") -> None:
    filter_any: Any = ...  # < we don't know the actual type and don't care
    async for item in a.filter(filter_any, aitr):
        print(2 + item)  # type: ignore

Request Assignment [Optional]

• I already understand the cause and want to submit a bugfix.

Start with the minimal async filter example and inspect the overload definitions for the referenced async filter API. Reproduce how an Any argument selects the special-case overload, then verify that overload resolution prefers the generic conservative case and that the example no longer takes the None-to-Never path.