rustdoc: use import stability marker in display

[notriddle]

Fixes #135078

[rustbot]

r? @fmease

rustbot has assigned @fmease.
They will have a look at your PR within the next two weeks and either review your PR or reassign to another reviewer.

Use r? to explicitly pick a reviewer

[camelid]

Thanks! r=me after addressing the comment on the test

[camelid]

LGTM, thanks. I do wonder whether there are cases opposite from what this fixes -- i.e. where the re-export stability is wrong and the original item is what we should use. I tested locally and found that #[unstable] on a re-export of a stable item is ignored by rustc.

But in the particular case this PR addresses, I think the new behavior overall makes more sense, so let's merge it.

[camelid]

@bors r+ rollup

[bors]

📌 Commit 916cfbc has been approved by camelid

It is now in the queue for this repository.

[bors]

⌛ Testing commit 916cfbc with merge a2016aa...

[bors]

☀️ Test successful - checks-actions
Approved by: camelid
Pushing a2016aa to master...

[rust-timer]

Finished benchmarking commit (a2016aa): comparison URL.

Overall result: ❌ regressions - no action needed

@rustbot label: -perf-regression

Instruction count

This is the most reliable metric that we have; it was used to determine the overall result at the top of this comment. However, even this metric can sometimes exhibit noise.

	mean	range	count
Regressions ❌ (primary)	-	-	0
Regressions ❌ (secondary)	0.4%	[0.4%, 0.4%]	1
Improvements ✅ (primary)	-	-	0
Improvements ✅ (secondary)	-	-	0
All ❌✅ (primary)	-	-	0

Max RSS (memory usage)

Results (primary -3.0%, secondary -1.0%)

This is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.

	mean	range	count
Regressions ❌ (primary)	-	-	0
Regressions ❌ (secondary)	-	-	0
Improvements ✅ (primary)	-3.0%	[-3.0%, -3.0%]	1
Improvements ✅ (secondary)	-1.0%	[-1.0%, -1.0%]	1
All ❌✅ (primary)	-3.0%	[-3.0%, -3.0%]	1

Cycles

This benchmark run did not return any relevant results for this metric.

Binary size

This benchmark run did not return any relevant results for this metric.

Bootstrap: 763.719s -> 764.824s (0.14%)
Artifact size: 326.09 MiB -> 326.07 MiB (-0.01%)