Update Rust crate criterion to v5

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
criterion (source)	dev-dependencies	major	4.4.1 → 5.0.0

---

Release Notes

CodSpeedHQ/codspeed-rust (criterion)

v5.0.0

Compare Source

💥 BREAKING

MSRV bumped to 1.85 for all packages: codspeed, codspeed-criterion-compat, codspeed-divan-compat

What's Changed

This release includes a fix for benchmark URI generation when users do not use the provided macros to declare their criterion main function.

• fix(criterion-compat): fix URI formatting when criterion_group!/criterion_main! are bypassed by @​not-matthias in #​169
• Fix lower bound of cc crate by @​konstin in #​182
• Update colored dep by @​rukai in #​142
• update getrandom to 0.4 by @​Ludea in #​177

New Contributors

• @​rukai made their first contribution in #​142
• @​Ludea made their first contribution in #​177

Full Changelog: CodSpeedHQ/codspeed-rust@v4.7.0...v5.0.0

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[codspeed-hq]

Merging this PR will not alter performance

🎉 Hooray! codspeed-rust just leveled up to 5.0.0!

A heads-up, this is a breaking change and it might affect your current performance baseline a bit. But here's the exciting part - it's packed with new, cool features and promises improved result stability 🥳!
Curious about what's new? Visit our releases page to delve into all the awesome details about this new version.

✅ 20 untouched benchmarks
⏩ 9 skipped benchmarks¹

---

_{Comparing renovate/criterion-5.x (32c782b) with main (f926cfd)}

Footnotes

1. 9 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩