Bump criterion from 0.4.0 to 0.5.1.

[martinfrances107]

As part of #1223 . This PR fixes this security advisory

Crate:     atty
Version:   0.2.14
Warning:   unsound
Title:     Potential unaligned read
Date:      2021-07-04
ID:        RUSTSEC-2021-0145
URL:       https://rustsec.org/advisories/RUSTSEC-2021-0145
Dependency tree:
atty 0.2.14
└── criterion 0.4.0
    └── chrono 0.5.0-alpha.1

[pitdicker]

This unfortunately doesn't work yet, because criterion has a higher MSRV. See #1104.

[pitdicker]

If you know a solution that would be great, I didn't look super deep into it.

[martinfrances107]

I will take a look over the weekend ... thanks for linking to the MSRV issue...
that broadened my perspective.

[djc]

This is a bit silly, because criterion is effectively a dev-dependency. If we treat it as such, we don't need it to uphold our MSRV.

[pitdicker]

Yes, but even as a dev-dependency it breaks our build because it requires newer cargo features (as you learned me in #1104 (comment)).

[djc]

Ahh, yes, I remember now.

[martinfrances107]

Just wanted to confirm bumping the "rust-version" to 1.60.0 will fix the problem ..

If this is an acceptable solution is a different question!!

[pitdicker]

Criterion is dropped as a dependency in #1243 (moved to a sub-crate and updated to 5.1).

@martinfrances107 Thank you for working on this!