ml-matches: fix performance trap (#41925)
While normally we try to only call `jl_type_morespecific` on types with
a non-empty intersection (to be more precise about ambiguity reporting),
the only work we would do here (if the intersect is empty) would also be
to call continue.
Fixes #41518
