fix: ignore glibc version in --target for checks

[rnag]

I found a minor bug when doing local testing with a cargo install --path . approach: if I pass a target along with glibc version like x86_64-unknown-linux-musl.2.17, it tries to install the target component as it includes glibc part when checking if it's installed in the toolchain. Ideally, it should exclude the part after . in the final target which we run checks against.

These changes should fix following issues:

• when determining same target as host, use starts_with instead, in case --target has a trailing glibc part
• when checking if target is installed in toolchain, use the target name before the ., so we can omit the glibc part in the check

[mbergkvist]

Will there be a 0.5.2 release with this?

[calavera]

@mbergkvist yes, probably today or tomorrow. I'll leave a comment in this thread when it's done

[calavera]

@mbergkvist released https://crates.io/crates/cargo-lambda/0.5.2

[mbergkvist]

Thanks!