inference: backward constraint propagation from call signatures

[aviatesk]

This PR implements another (limited) backward analysis pass in abstract interpretation; it exploits signatures of matching methods and refines types of slots.

Here are couple of examples where these changes will improve the accuracy:

generic function example

addint(a::Int, b::Int) = a + b
@test Base.infer_return_type((Any,Any,)) do a, b
    c = addint(a, b)
    return a, b, c # now the compiler understands `a::Int`, `b::Int`
end == Tuple{Int,Int,Int}

typeassert example

@test Base.infer_return_type((Any,)) do a
    a::Int
    return a # now the compiler understands `a::Int`
end == Int

Unlike Conditional constrained type propagation, this type refinement information isn't encoded within any lattice element, but rather they are propagated within the newly added field frame.curr_stmt_change of frame::InferenceState.
For now this commit exploits refinement information available from call signatures of generic functions and typeassert.

---

• closes inference: if it doesn't know how to quack, it can't be a duck #37866
• fixes Missing Pi node after type assert (or, using the non type asserted SSA value leads to worse inference) #38274
• closes doc: manual: performance tips: warn against suboptimal type asserts #55115

[jishnub]

Closes #55115

[aviatesk]

@nanosoldier runbenchmarks("inference", vs=":master")

[nanosoldier]

Your benchmark job has completed - possible performance regressions were detected. A full report can be found here.

[aviatesk]

@nanosoldier runbenchmarks("inference", vs=":master")

[nanosoldier]

Your benchmark job has completed - possible performance regressions were detected. A full report can be found here.

[aviatesk]

@nanosoldier runbenchmarks("inference", vs=":master")

[nanosoldier]

Your benchmark job has completed - possible performance regressions were detected. A full report can be found here.

[aviatesk]

@nanosoldier runbenchmarks("inference", vs=":master")

[aviatesk]

Ok, I fixed all inference performance regressions, and this should be ready to go now.

[nanosoldier]

Your benchmark job has completed - possible performance regressions were detected. A full report can be found here.

[aviatesk]

@nanosoldier runbenchmarks("inference", vs=":master")

[nanosoldier]

Your benchmark job has completed - possible performance regressions were detected. A full report can be found here.

[aviatesk]

Going to merge. Post reviews would be very welcomed, but at the same time we don't need to wait for reviews before merging.

[nsajko]

This doesn't seem like it's been completely effective yet: #55278