Bump Chrono to 0.4.22 and remove time 0.1

[pinkforest]

Signed-off-by: Miss M MissM_signed@protonmail.ch

This PR resolves two below security advisories:

RUSTSEC-2020-0159, RUSTSEC-2020-0071 - When doing env & time same time - it's not thread safe

Chrono from 0.4.20 has a new maintainer and did a lot of fixes including RiR localtime_r 🥳

time 0.1 in turn is brought by chrono "oldtime" feature that is "optional" (but default) chrono dependency

default = ["clock", "std", "oldtime", "wasmbind"] -> oldtime = ["time"]

But time 0.1 was included via common & inspect as chrono was imported with default features

I've set the features explicitly leaving out oldtime that is not considered thread safe and wasmbind we don't need either

By specifying the feature explicitly we got rid of time 0.1 🥳

Then I had also - in order to bump the .lock more precisely for chrono 0.4.22 do:

$ cargo update -p chrono

    Updating crates.io index
    Updating chrono v0.4.19 -> v0.4.20

libc was holding back chrono bump to 0.4.22 so:

$ cargo update -p libc

    Updating crates.io index
    Updating libc v0.2.125 -> v0.2.132

$ cargo update -p chrono --precise 0.4.22

    Updating crates.io index
      Adding android_system_properties v0.1.4
    Updating chrono v0.4.20 -> v0.4.22
      Adding iana-time-zone v0.1.46
    Updating js-sys v0.3.57 -> v0.3.58
    Updating wasm-bindgen v0.2.80 -> v0.2.81
    Updating wasm-bindgen-backend v0.2.80 -> v0.2.81
    Updating wasm-bindgen-macro v0.2.80 -> v0.2.81
    Updating wasm-bindgen-macro-support v0.2.80 -> v0.2.81
    Updating wasm-bindgen-shared v0.2.80 -> v0.2.81

[cloudhead]

Nothing better than getting rid of dependencies