fix: Skip pattern analysis on type mismatches

[ShoyuVanilla]

Fixes #19844

Playing with tracings on rustc, I found that it never enters rustc_pattern_analysis if there exists any typecheck error inside the given body:

• Entrypoint for pattern analysis
• Short circuit on tcx.thir_body()?
• tcx.thir_body() implementation

We've been doing simillar "skip on type-error" things on the following lines:

rust-analyzer/crates/hir-ty/src/diagnostics/expr.rs

Lines 210 to 225 in 7230ded

	// We only include patterns whose type matches the type
	// of the scrutinee expression. If we had an InvalidMatchArmPattern
	// diagnostic or similar we could raise that in an else
	// block here.
	//
	// When comparing the types, we also have to consider that rustc
	// will automatically de-reference the scrutinee expression type if
	// necessary.
	//
	// FIXME we should use the type checker for this.
	if (pat_ty == scrut_ty
	|| scrut_ty
	.as_reference()
	.map(|(match_expr_ty, ..)| match_expr_ty == pat_ty)
	.unwrap_or(false))
	&& types_of_subpatterns_do_match(arm.pat, &self.body, &self.infer)

rust-analyzer/crates/hir-ty/src/diagnostics/expr.rs

Lines 160 to 163 in 7230ded

	if self.infer.expr_type_mismatches().next().is_some() {
	// FIXME: Due to shortcomings in the current type system implementation, only emit
	// this diagnostic if there are no type mismatches in the containing function.
	} else if let Expr::MethodCall { receiver, .. } = expr {

But unfortunately not on the line in this PR