Further upgrade jiff to fix fuzz failures (#1984)

This upgrades `jiff` to 0.2.12 to fix fuzzing failures. The test
case introduced in the previous commit now passes.

Upgrading `jiff` past 0.2.11 gets the fix for BurntSushi/jiff#359,
fixed in BurntSushi/jiff#360. To avoid declaring compatibility with
a version that has the bug, this advances `jiff` from 0.2.10 to
0.2.12 in the `gix-archive` and `gix-date` manifests.

(The changes in `Cargo.lock` are those that occur automatically
when `cargo check --workspace` is run after those changes.)

Fixes #1979
Fixes #1982

Author: EliahKagan

Cargo.lock

@@ -35,7 +35,7 @@ gix-date = { version = "^0.10.1", path = "../gix-date" }
 
 flate2 = { version = "1.1.1", optional = true, default-features = false, features = ["zlib-rs"] }
 zip = { version = "2.6.1", optional = true, default-features = false, features = ["deflate"] }
-jiff = { version = "0.2.10", default-features = false, features = ["std"] }
+jiff = { version = "0.2.12", default-features = false, features = ["std"] }
 
 thiserror = "2.0.0"
 bstr = { version = "1.12.0", default-features = false }

gix-archive/Cargo.toml

@@ -22,7 +22,7 @@ serde = ["dep:serde", "bstr/serde"]
 bstr = { version = "1.12.0", default-features = false, features = ["std"] }
 serde = { version = "1.0.114", optional = true, default-features = false, features = ["derive"] }
 itoa = "1.0.1"
-jiff = "0.2.10"
+jiff = "0.2.12"
 thiserror = "2.0.0"
 # TODO: used for quick and easy `TimeBacking: std::io::Write` implementation, but could make that `Copy`
 #       and remove this dep with custom impl

gix-date/Cargo.toml

@@ -330,6 +330,7 @@ mod fuzz {
     fn reproduce_1979() {
         gix_date::parse("fRi ", None).ok();
     }
+
     #[test]
     fn invalid_but_does_not_cause_panic() {
         for input in ["-9999-1-1", "7	-𬞋", "5 ڜ-09", "-4 week ago Z", "8960609 day ago"] {