[test] Enable sha2-asm feature

[pierwill]

Extends #93863. See #93973.

[rust-highfive]

r? @Mark-Simulacrum

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

[pierwill]

@rustbot author

[pierwill]

@bors try @rust-timer queue

[rust-timer]

Awaiting bors try build completion.

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

[bors]

⌛ Trying commit 8b2a00a with merge b3a300610235a24445d5a0ba7314673205130e46...

[klensy]

This perf run will show deps bump + feature difference, not sha2-asm feature difference

[pierwill]

This perf run will show deps bump + feature difference, not sha2-asm feature difference

Ah, yes—thanks. 😇 Info could still be useful, but we'll want to do another run.

[pierwill]

(@Mark-Simulacrum Is there a way to cancel an in-progress perf run?)

[bors]

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

[rust-timer]

Queued b3a300610235a24445d5a0ba7314673205130e46 with parent b321742, future comparison URL.

[rust-timer]

Finished benchmarking commit (b3a300610235a24445d5a0ba7314673205130e46): comparison url.

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

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