Avoid adjusting TLS data twice for queries

[cjgillot]

Based on #86038

Each query adjusts TLS information twice: once to adjust job id and record diagnostics, and once to record dependencies. This PR attempts to do it only once using dedicated functions for queries.

r? @Mark-Simulacrum
Blocked on #86038

[cjgillot]

@bors try @rust-timer queue

[rust-timer]

Awaiting bors try build completion.

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

[bors]

⌛ Trying commit 30b9d2b2726897caf735d37a6513a827c28d2744 with merge 019045026f3de24da13181f3957033803b0451a2...

[bors]

☀️ Try build successful - checks-actions
Build commit: 019045026f3de24da13181f3957033803b0451a2 (019045026f3de24da13181f3957033803b0451a2)

[rust-timer]

Queued 019045026f3de24da13181f3957033803b0451a2 with parent e015ef5, future comparison URL.

[rust-timer]

Finished benchmarking commit (019045026f3de24da13181f3957033803b0451a2): comparison url.

Summary: This change led to large relevant mixed results 🤷 in compiler performance.

• Large improvement in instruction counts (up to -1.4% on incr-full builds of unused-warnings)
• Moderate regression in instruction counts (up to 0.6% on full builds of inflate)

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.

Next Steps: If you can justify the regressions found in this try perf run, please indicate this with @rustbot label: +perf-regression-triaged along with sufficient written justification. If you cannot justify the regressions please fix the regressions and do another perf run. If the next run shows neutral or positive results, the label will be automatically removed.

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

[Mark-Simulacrum]

r=me, but let's confirm perf after #86038 merges

[bors]

☔ The latest upstream changes (presumably #90210) made this pull request unmergeable. Please resolve the merge conflicts.