Fix security audit - get rid of chrono and use time directly

[AurelienFT]

Chrono still use a very old version of time (0.1 now it's 0.3). They have a PR running since months for updating but it seems that there is communication problems that lead to long time development. The PR : chronotope/chrono#639

This break our CI like a lot of others projects that use cargo audit. A lot of projects that use chrono to do things that are now implemented in the new version of time has switched to use time directly instead of using tokio. Some examples :

• Tracking issue for fixing chrono crate dependencies brave/brave-browser#20568
• Get rid of chrono in favor of time meilisearch/milli#450

So as we also only use chrono to make things that now possible in time which is more maintained I suggest in this PR a change to use time instead of chrono. So that it will fix our CI and make us use a more maintained dependency.

Fix #2374

[AureliaDolo]

Just the clippy warning left to fix and LGTM

By the way if you have an idea to better implement days_hours_mins_secs

[AurelienFT]

Just the clippy warning left to fix and LGTM

By the way if you have an idea to better implement days_hours_mins_secs

Good catch ! Fixed ! Thank you.

[AureliaDolo]

And I'm wondering why there is an unwrap in to_utc_string but eh

[AurelienFT]

bors merge

[bors]

Build succeeded:

• build