Fix missing_inline_in_public_items fail to fulfill expect in --test build

[profetia]

Closes #13394

changelog: [missing_inline_in_public_items] fix failure to fulfill expect in --test build

[rustbot]

r? @y21

rustbot has assigned @y21.
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

[y21]

This does mean that something like #[expect(clippy::missing_inline_in_public_items)] fn private_function() {} passes the expectation with --test even though the lint would never emit a warning there, but I'm not really sure how we could avoid that so this seems fine

[Alexendoo]

This looks like a symptom rather than the root of the issue, that the following is a false negative when ran with cargo clippy --tests

#![warn(clippy::missing_inline_in_public_items)]

pub fn foo() -> u32 {
    0
}

It should still lint foo as it would for cargo clippy

[profetia]

Hmm.. Im confused. What is the expected behavior in --test ?

[profetia]

I doubt if it is possible to know the original crate type in --test

[profetia]

r? clippy