Renaming isn't aware of different namespaces

Given the following source:

mod foo {
    pub mod bar {
        pub fn inner() {}
    }
    pub const bar: () = ();
}
use foo::bar;
fn main() {
    bar::inner();
}

renaming the const bar to something else like bar2 breaks the code as it emits:

mod foo {
    pub mod bar {
        pub fn inner() {}
    }
    pub const bar2: () = ();
}
use foo::bar2;
fn main() {
    bar::inner(); // now unresolved
}

The general problem already exists for path resolution as the preference there is kind of hardcoded at the moment, but even with that fixed renaming requires knowledge of whether a reference might be occupying multiple namespaces or not in use statements.

For consts this isn't too pressing of a matter as the capitalization is usually different, but for macros this can cause problems more easily as those names tend to clash with modules/functions.

Start with the rename implementation and its path-resolution handling, then trace how use statements and references are classified across Rust namespaces. Reproduce the example and verify that renaming the const preserves the module reference while also updating references that actually target the const, including macro-related cases.