Bug 1990382 - chore: upgrade chrono 0.4.41 → 0.4.42, windows-link 0.1 → 0.2 r=#supply-chain-reviewers

Some common dependencies are starting to consume `windows-link` 0.2,
like `backtrace` with
<rust-lang/backtrace-rs#727>. This is going to
become increasingly common, as crates previously targeting
`windows-target` and `windows-sys` realize they can use `windows-link`
for the small set of Windows platform APIs they actually need.

This is the shortest path to start consuming `windows-link` 0.2, and
I think it turned out to be pretty easy to review!

Differential Revision: https://phabricator.services.mozilla.com/D265914

Author: ErichDonGubler

Cargo.lock

@@ -1326,6 +1326,11 @@ criteria = "safe-to-deploy"
 delta = "0.4.19 -> 0.4.40"
 notes = "Significant refactor of both implementation and dependencies."
 
+[[audits.chrono]]
+who = "Erich Gubler <[email protected]>"
+criteria = "safe-to-deploy"
+delta = "0.4.41 -> 0.4.42"
+
 [[audits.chunked_transfer]]
 who = "Glenn Watson <[email protected]>"
 criteria = "safe-to-deploy"
@@ -7077,6 +7082,11 @@ criteria = "safe-to-deploy"
 version = "0.1.1"
 notes = "A microsoft crate allowing unsafe calls to windows apis."
 
+[[audits.windows-link]]
+who = "Erich Gubler <[email protected]>"
+criteria = "safe-to-deploy"
+delta = "0.1.1 -> 0.2.0"
+
 [[audits.winreg]]
 who = "Ray Kraesig <[email protected]>"
 criteria = "safe-to-run"