feat: Add the ability to jump from into to from definitions

[1hakusai1]

close #18316
close #15315
(maybe related to #4558)

This PR add the ability to jump from into to from definitions.

• from into to from
• from try_into to try_from
• from parse to from_str

Test

I can't write unit tests for TryFrom and FromStr because minicore doesn't contain them.

use std::str::FromStr;

struct SourceType;

struct TargetType;

impl Into<i64> for SourceType {
    // E
    fn into(self) -> i64 {
        todo!()
    }
}

impl TryInto<String> for SourceType {
    type Error = String;

    // F
    fn try_into(self) -> Result<String, Self::Error> {
        todo!()
    }
}

impl From<SourceType> for TargetType {
    // A
    fn from(value: SourceType) -> Self {
        todo!()
    }
}

impl FromStr for TargetType {
    type Err = String;

    // D
    fn from_str(s: &str) -> Result<Self, Self::Err> {
        todo!()
    }
}

impl From<i64> for TargetType {
    // B
    fn from(value: i64) -> Self {
        todo!()
    }
}

impl TryFrom<String> for TargetType {
    type Error = String;

    // C
    fn try_from(value: String) -> Result<Self, Self::Error> {
        todo!()
    }
}

fn main() {
    // into to from
    let source = SourceType;
    let target: TargetType = source.into(); // goto A
    let target: TargetType = 12.into(); // goto B

    // try_into to try_from
    let maybe_target: Result<TargetType, _> = String::from("aaa").try_into(); // goto C

    // parse to from_str
    let maybe_target: Result<TargetType, String> = "aaaaa".parse(); // goto D

    // regular cases
    let source = SourceType;
    let integer: i64 = source.into(); // goto E
    let source = SourceType;
    let string: Result<String, _> = source.try_into(); // goto F
}

[1hakusai1]

I think this works in many cases but does not cover all cases.

If someone knows how to check type compatibilities, please comment.
Maybe this feature is required to cover all cases.

[ChayimFriedman2]

I can't write unit tests for TryFrom and FromStr because minicore doesn't contain them.

Feel free to add them to minicore (behind flags).

[ChayimFriedman2]

I think we actually need the adjusted type for the receiver.

[Veykril]

We should use Semantics::resolve_method_call_as_callable here, that gives us a bunch of the things here already like receiver param/type, function id and return type.

[Veykril]

This should be going through the (currently unexposed) SourceAnalyzer::resolve_impl_method_or_trait_def function

[Veykril]

I'll touch up on this a bit in a follow up PR for some style nits, but otherwise lgtm 👍

[Veykril]

Fwiw we should also make this work with non method call syntax, but that can wait for a follow up PR