Improve effects analysis for indirect calls

[stevenfontanella]

We currently give up computing effects for indirect calls in Binaryen, which halts many optimizations. We can come up with more precise effects in the closed-world case by aggregating the effects of all functions of the given function type into the indirect call.

• Aggregate indirect call effects at the function level (Compute effects for indirect calls in GlobalEffects #8609)
• Aggregate indirect call effects for individual call expressions (Effect analysis for indirect call expressions #8625)
• Prune effects for functions that aren't addressed (Account for unaddressed funcs in GlobalEffects #8644)
• Prune effects for indirect calls to exact types (Account for exact references in indirect call effects #8807)
• Use indirect call effects in LinearExecutionWalker to allow more optimizations for passes (Use indirect call effects in LinearExecutionWalker #8738)
• Optimize indirect calls to uninhabited types to (unreachable)
• Optimize indirect calls to private types in open world