Our module path exploration does not match rustc's

Given a lib.rs or main.rs with:

mod outline;

With outline.rs defined as:

const _: () = {
    mod inline {
        #[path = "pathed.rs"]
        mod pathed;
    }
};

rustc attempts to load: src/inline/pathed.rs
r-a attempts to load: src/inline/pathed.rs

But with outline.rs defined as:

mod inline {
    const _: () = {
        mod inline {
            #[path = "pathed.rs"]
            mod pathed;
        }
    };
}

rustc attempts to load: src/outline/inline/inline/pathed.rs
r-a attempts to load: src/inline/inline/pathed.rs

This is apparently expected behaviour (I'd like to say it is not), though I don't quite fully grasp why: https://rust-lang.zulipchat.com/#narrow/stream/122651-general/topic/Surprising.20behaviour.20with.20.23.5Bpath.5D.20and.20block.20scopes

Start with the linked Zulip discussion, then reproduce the two module layouts using lib.rs or main.rs and outline.rs. Compare rustc's and rust-analyzer's attempted paths; done means rust-analyzer resolves the nested #[path] module to the same path as rustc.