[perf experiment] resolve: Do not cache nearest parent mod in ModuleData

[petrochenkov]

No description provided.

[rust-highfive]

r? @oli-obk

(rust-highfive has picked a reviewer for you, use r? to override)

[petrochenkov]

@bors try @rust-timer queue

[rust-timer]

Awaiting bors try build completion.

@rustbot label: +S-waiting-on-perf

[bors]

⌛ Trying commit 8443ea9 with merge 73ea2bd112a8b357f9754dd10fb68933bb71f6b7...

[bors]

☀️ Try build successful - checks-actions
Build commit: 73ea2bd112a8b357f9754dd10fb68933bb71f6b7 (73ea2bd112a8b357f9754dd10fb68933bb71f6b7)

[rust-timer]

Queued 73ea2bd112a8b357f9754dd10fb68933bb71f6b7 with parent 9bb77da, future comparison URL.

[rust-timer]

Finished benchmarking commit (73ea2bd112a8b357f9754dd10fb68933bb71f6b7): comparison url.

Summary: This benchmark run did not return any relevant changes.

If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf.

Benchmarking this pull request likely means that it is perf-sensitive, so we're automatically marking it as not fit for rolling up. While you can manually mark this PR as fit for rollup, we strongly recommend not doing so since this PR led to changes in compiler perf.

@bors rollup=never
@rustbot label: +S-waiting-on-review -S-waiting-on-perf -perf-regression