fix build - BenchmarkDotNet Version

[AnkushinDaniil]

Summary

Bump BenchmarkDotNet and BenchmarkDotNet.Diagnostics.Windows from 0.16.0-nightly.20260320.468 to 0.16.0-nightly.20260322.472.

The pinned .468 build was unpublished from NuGet and is no longer restorable, which fails the Build matrix on master and every open PR with NU1603 (treated as error). NuGet auto-resolves to .472 as the nearest available nightly.

Recurrence of the same failure mode as #11152 (which bumped .466 → .468 five days ago).

CI error

error NU1603: Warning As Error: Nethermind.Precompiles.Benchmark.Test depends on
BenchmarkDotNet (>= 0.16.0-nightly.20260320.468) but BenchmarkDotNet
0.16.0-nightly.20260320.468 was not found. BenchmarkDotNet
0.16.0-nightly.20260322.472 was resolved instead.

[claude]

Claude finished @AnkushinDaniil's task in 51s —— View job

---

Review

• Read changed file (Directory.Packages.props)
• Loaded package management rules
• Analyzed changes

---

Verdict: LGTM — no issues found.

The change is minimal and surgical:

• Both BenchmarkDotNet and BenchmarkDotNet.Diagnostics.Windows are bumped together to the same version 0.16.0-nightly.20260322.472, maintaining the required version alignment between the two packages.
• The update is correctly placed only in Directory.Packages.props per the repo's Central Package Management (CPM) rules — no .csproj files touched.
• The root cause is well-described: .468 was unpublished from NuGet causing a hard NU1603 build failure; .472 is the next available nightly.

No critical, high, or medium issues.

Low / informational: The repo is now pinned to a nightly build for the third time in a short window (.466 → .468 → .472). As a long-term consideration, tracking whether BenchmarkDotNet has a stable 0.16.0 release or pinning to a known-stable nightly could reduce CI noise — but that's out of scope for this emergency fix.

[svlachakis]

We have fixed that 3 times last week, should we consider using stable release? @LukaszRozmej @benaadams @kamilchodola ?

[benaadams]

We have fixed that 3 times last week, should we consider using stable release? @LukaszRozmej @benaadams @kamilchodola ?

When the next make a stable release