Robustify and genericize return-type-notation resolution in resolve_bound_vars

[compiler-errors]

#129629 implemented return-type-notation (RTN) in its path form, like where T::method(..): Bound. As part of lowering, we must record the late-bound vars for the where clause introduced by the method (namely, its early- and late-bound lifetime arguments, since where T::method(..) turns into a higher-ranked where clause over all of the lifetimes according to RFC 3654).

However, this logic was only looking at the where clauses of the item that the T::method(..) item was written, and not any parent items. This PR generalizes that logic to look at the parent item (i.e. the outer impl or trait) instead and fixes a (debug only) assertion as an effect.

This logic is also more general and likely easier to adapt to more interesting (though likely very far off) cases like non-lifetime binder for<T: Trait> T::method(..): Send bounds.

[rustbot]

r? @pnkfelix

rustbot has assigned @pnkfelix.
They will have a look at your PR within the next two weeks and either review your PR or reassign to another reviewer.

Use r? to explicitly pick a reviewer