perf-check: Revert "Rollup merge of #87596"

[JohnTitor]

Checking the perf regression in #87640 (comment).
Only this PR touches rustc_ast in the rollup and it should affect the bootstrap time at least, let's see if this also causes the regression.
r? @ghost cc @Mark-Simulacrum

[JohnTitor]

@bors try @rust-timer queue

[rust-timer]

Awaiting bors try build completion.

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

[bors]

⌛ Trying commit 3bb7c34 with merge 2d70f86f6aa403c306f136178065b8ac93190aac...

[bors]

☀️ Try build successful - checks-actions
Build commit: 2d70f86f6aa403c306f136178065b8ac93190aac (2d70f86f6aa403c306f136178065b8ac93190aac)

[rust-timer]

Queued 2d70f86f6aa403c306f136178065b8ac93190aac with parent 2939249, future comparison URL.

[rust-timer]

Finished benchmarking try commit (2d70f86f6aa403c306f136178065b8ac93190aac): comparison url.

Summary: This benchmark run did not return any significant 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.

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

[JohnTitor]

Seems this one isn't, closing.