Emit delayed bug instead of ICEing when TypeOutlives goal fails

[ShoyuVanilla]

Fixes #161527

They can actually fail with the next-solver 😄

rust/compiler/rustc_next_trait_solver/src/solve/mod.rs

Lines 88 to 93 in 2e071b2

	fn compute_type_outlives_goal(
	&mut self,
	goal: Goal<I, ty::OutlivesClause<I, I::Ty>>,
	) -> QueryResultOrRerunNonErased<I> {
	let ty::OutlivesClause(ty, lt) = goal.predicate;
	let ty = self.normalize(GoalSource::Misc, goal.param_env, ty::Unnormalized::new_wip(ty))?;

I have once considered tinkering proof tree/find_best_leaf_obligation to make it suggest the failed normalization goal but I doubt it worths the extra complexity, since we prolly already have other failing obligations in these cases

r? adwinwhite

[adwinwhite]

The diagnostics is strange in the first place. How do we get (): Z<'a, () bound? But that's another problem and we can track it separately.

@bors r+ rollup

[rust-bors]

📌 Commit 44febdf has been approved by adwinwhite

It is now in the queue for this repository.

[ShoyuVanilla]

The diagnostics is strange in the first place. How do we get (): Z<'a, () bound?

It happens like this, strangely recursive 😄

`Z<'a, T>` is well-formed
    `Z<'a, T>`'s where-bound `T: Z<'a, ()>` is well-formed
        `Z<'a, ()>` is well-formed
            `(): Z<'a, ()>` (`Z`'s where bound on its param `T = ()`)

[rust-timer]

Note

This PR was benchmarked as part of triage of its containing rollup: triage URL.

Finished benchmarking commit (f797fd8): comparison URL.

Overall result: no relevant changes - no action needed

@rustbot label: -perf-regression

Instruction count

This perf run didn't have relevant results for this metric.

Max RSS (memory usage)

Results (secondary -0.9%)

A less reliable metric. May be of interest, but not used to determine the overall result above.

	mean	range	count
Regressions ❌ (primary)	-	-	0
Regressions ❌ (secondary)	-	-	0
Improvements ✅ (primary)	-	-	0
Improvements ✅ (secondary)	-0.9%	[-0.9%, -0.9%]	1
All ❌✅ (primary)	-	-	0

Cycles

This perf run didn't have relevant results for this metric.

Binary size

This perf run didn't have relevant results for this metric.

Bootstrap: missing data
Artifact size: 307.41 MiB -> 402.64 MiB (30.98%)