Suggest `Some(&v)` rather than `Some(v.clone())` when calling generic owning methods

Code

#[allow(unused)]
fn f() {
    let v = vec![0];
    Some(v).is_some_and(|_| true);
    drop(v);
}

Current output

Compiling playground v0.0.1 (/playground)
error[E0382]: use of moved value: `v`
 --> src/lib.rs:5:10
  |
3 |     let v = vec![0];
  |         - move occurs because `v` has type `Vec<i32>`, which does not implement the `Copy` trait
4 |     Some(v).is_some_and(|_| true);
  |          - value moved here
5 |     drop(v);
  |          ^ value used here after move
  |
help: consider cloning the value if the performance cost is acceptable
  |
4 |     Some(v.clone()).is_some_and(|_| true);
  |           ++++++++

For more information about this error, try `rustc --explain E0382`.
error: could not compile `playground` (lib) due to 1 previous error

Desired output

Compiling playground v0.0.1 (/playground)
error[E0382]: use of moved value: `v`
 --> src/lib.rs:5:10
  |
3 |     let v = vec![0];
  |         - move occurs because `v` has type `Vec<i32>`, which does not implement the `Copy` trait
4 |     Some(v).is_some_and(|_| true);
  |          - value moved here
5 |     drop(v);
  |          ^ value used here after move
  |
help: consider borrowing the value
  |
4 |     Some(&v).is_some_and(|_| true);
  |          +

For more information about this error, try `rustc --explain E0382`.
error: could not compile `playground` (lib) due to 1 previous error

Rationale and extra context

No response

Other cases

No response

Rust Version

1.80.0-nightly

(2024-05-18 b1ec1bd65f89c1375d2c)

Anything else?

No response

Start by reproducing the supplied Rust 1.80.0-nightly snippet and comparing the current E0382 help text with the desired output. Trace the compiler diagnostic suggestion for this generic owning-method case; done when the suggestion prefers borrowing with &v rather than cloning and the reported example is covered.