fix: only ref match non-unknown value items

[A4-Tacks]

Fixes #22324

Example

struct S<T>(T);
impl<T> core::ops::Deref for S<T> {
    type Target = T;
}
fn foo<T>(s: &u32) {}
fn main() {
    let ssss = S();
    foo($0);
}

Before this PR

lc ssss S<{unknown}> [local]
lc &ssss [type+local]
st S S<{unknown}> []
st &S [type]
...

After this PR

lc ssss S<{unknown}> [local]
st S S<{unknown}> []
...

[A4-Tacks]

r? @ChayimFriedman2 This needs to be fixed as soon as possible, otherwise any Deref to generic will be auto imported

Example

fn foo(_: &u32) {}
fn main() {
    foo(M$0);
}

Completes

&MutexGuard~(use std::sync::MutexGuard)
&MutexGuard~(use std::sync::nonpoison::MutexGuard)
&ManuallyDrop~(use std::mem::ManuallyDrop)
&MappedMutexGuard~(use std::sync::MappedMutexGuard)
&MappedMutexGuard~(use std::sync::nonpoison::MappedMutexGuard)
&MappedRwLockReadGuard~(use std::sync::MappedRwLockReadGuard)
&MappedRwLockReadGuard~(use std::sync::nonpoison::MappedRwLockReadGuard)
&MappedRwLockWriteGuard~(use std::sync::MappedRwLockWriteGuard)
&MappedRwLockWriteGuard~(use std::sync::nonpoison::MappedRwLockWriteGuard)

[ChayimFriedman2]

Why do you know filter to only consts/statics/locals?

View changes since the review

[A4-Tacks]

For struct paths, etc., the assoc fn may not necessarily return Self, and it is suggest to reference noise

And if its method is still ref match, it can be done when completing the method e.g f(Foo::ne) -> f(&Foo::new())

[ChayimFriedman2]

But this will also prevent struct literals from adding a ref, e.g. Foo { ... } or Foo(...).

[A4-Tacks]

No, this is not. The test was not broken, and it was rendered by literal instead of path

[ChayimFriedman2]

Which test?

[A4-Tacks]

@ChayimFriedman2 Look at this test

View changes since the review