rustdoc: Remove unnecessary provided_trait_methods field from Impl

[jyn514]

It can be calculated on-demand.

Helps with #76382.

[rust-highfive]

r? @CraftSpider

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

[jyn514]

@bors try @rust-timer queue

[rust-timer]

Awaiting bors try build completion.

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

[bors]

⌛ Trying commit bb1a5dd05219bfb178be98baf976464c9ebd2f8a with merge 1e800a725cbcb3b7f29c5cb704e0f85f3db7aabd...

[bors]

☀️ Try build successful - checks-actions
Build commit: 1e800a725cbcb3b7f29c5cb704e0f85f3db7aabd (1e800a725cbcb3b7f29c5cb704e0f85f3db7aabd)

[rust-timer]

Queued 1e800a725cbcb3b7f29c5cb704e0f85f3db7aabd with parent 7f4afdf, future comparison URL.

[rust-timer]

Finished benchmarking try commit (1e800a725cbcb3b7f29c5cb704e0f85f3db7aabd): comparison url.

Benchmarking this pull request likely means that it is perf-sensitive, so we're automatically marking it as not fit for rolling up. Please note that if the perf results are neutral, you should likely undo the rollup=never given below by specifying rollup- to bors.

Importantly, though, if the results of this run are non-neutral do not roll this PR up -- it will mask other regressions or improvements in the roll up.

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

[jyn514]

Around -.3% in instruction counts across the board, except regex which regressed by .3%. Up to -1.8% max rss with no major regressions. I think that tradeoff is worth it.

[CraftSpider]

Code looks good to me, I agree with the trade-off analysis. Needs a rebase to fix conflicts, then it should be good. I also appreciate the minor code deduplication :P

[CraftSpider]

@rustbot label: -S-waiting-on-review +S-waiting-on-author

[jyn514]

@bors r=CraftSpider

[bors]

📌 Commit b1f5917 has been approved by CraftSpider

[bors]

⌛ Testing commit b1f5917 with merge 3d67e07...

[bors]

☀️ Test successful - checks-actions
Approved by: CraftSpider
Pushing 3d67e07 to master...