Suggest a solution to confusing precedence issues related to Borrow / RefCell

What it does

This lint would catch a common mistake with RefCell / Borrow, where Borrow::borrow can confusingly take precedence over RefCell::borrow, resulting in incredibly unhelpful diagnostics that are unrelated to the problem (see: https://github.com/rust-lang/rust/issues/94858).

Ideally this should be fixed in the compiler itself, but it would also be nice to have a lint to catch this issue, since it's a fairly common issue that tends to bite new users.

Advantage

No response

Drawbacks

No response

Example

use std::{borrow::BorrowMut, cell::RefCell, rc::Rc};

pub struct Foo {
    bar: (),
}

fn foo() {
    let foo = Rc::new(RefCell::new(Foo { bar: () }));
    // lint here: consider explicitly specifying either RefCell::borrow_mut or BorrowMut::borrow_mut
    let bar = foo.borrow_mut().bar;
}

Could be written as:

use std::{borrow::BorrowMut, cell::RefCell, rc::Rc};

pub struct Foo {
    bar: (),
}

fn foo() {
    let foo = Rc::new(RefCell::new(Foo { bar: () }));
    let bar = RefCell::borrow_mut(&foo).bar;
}

Start with the RefCell/Borrow example in the issue and read the referenced rust-lang/rust#94858 discussion to understand the precedence problem. The work is done when Clippy can identify this confusing call pattern and provide guidance to explicitly select RefCell::borrow_mut or BorrowMut::borrow_mut.