Don't report "expression contains 'Any'" if it's a `TypeOfAny.from_error`

Update

@A5Rocks idea about not reporting expression contains Any if it's TypeOfAny.from_error is based 100. I also realized that if it's <nothing> it would still complain about attribute access etc being incorrect.

Bug Report
The reason being that when you update an overloaded signature you can get hundreds of reported "Expression contains 'Any'" errors, when there are in reality an order of magnitude less actual errors.

from typing import overload

@overload
def foo(a: int) -> int: ...
# this overload was just removed
# @overload
# def foo(a: None) -> str ...
@overload
def foo(a: str) -> str: ...
def foo(a: object) -> object: ...

a = foo(None)  # error: No overload variant of "foo" matches argument type "None"\
    # error: Expression has type "Any"

reveal_type(a)  # error: Expression has type "Any"\
  # note: Revealed type is "Any"
print(a) # error: Expression has type "Any"
bar(a) # error: Expression has type "Any"
a + "asdf" # error: Expression has type "Any"

But If TypeOfAny.from_errors are ignored:

a = foo(None)  # error: No overload variant of "foo" matches argument type "None"

reveal_type(a)  # note: Revealed type is "Any"
print(a)
bar(a)
a + "asdf"

Original Title

Invocations of overloaded functions with invalid argument types shouldn't return Any it should return <nothing>

Beginne mit den minimalen Beispielen für überladene Aufrufe im Issue und verfolge, wie die Auflösung ungültiger Überladungen TypeOfAny.from_error zuweist und wie spätere Ausdrücke diesen Typ melden. Als abgeschlossen gilt die Änderung, wenn der ursprüngliche Überladungsfehler bestehen bleibt, während weitergegebene Any-Werte mit Fehlerstatus keine zusätzlichen Diagnosen "Expression has type Any" erzeugen; im Issue werden keine Dateien oder auszuführenden Tests genannt.