Rust: Unify call resolution logic

[hvitved]

I was investigating a type inference performance issue on tayu0110/exml, and came up with a small reproduction case (first commit), which revealed that we are not correctly handling resolution of calls to non-method associated functions when the argument used to resolve the call has multiple trait bounds.

For method calls we are handling multiple trait bounds correctly since #21043, so the obvious solution would be to replicate this logic for non-method calls as well.

However, with #21217 we have:

As for calls to methods, we now also always check the Self type for calls to associated non-methods f.

which allows us to instead unify the resolution logic for calls to methods (module MethodResolution) and calls to non-methods (module NonMethodResolution) in a single implementation encompassing calls to all associated functions (module AssocFunctionResolution). Calls to non-associated functions does not rely on type inference (but instead on path resolution only), which is handled in the class NonAssocCallExpr.

Just like we can unify call resolution logic, we can also unify propagation of type information for resolved calls for calls to methods (module MethodCallMatching) and calls to non-methods (module NonMethodCallMatching) in a single implementation (module FunctionCallMatching), and type inference for tuple-like variant and struct constructions such as Option::Some(42) is then done in a separate module TupleLikeConstructionMatching.

LOC removed