zig: update to 0.14.0-dev

[nektro]

updates bun to use Zig 0.14.0-dev.2987+183bb8b08

PR'd upstream (non-blocking):

• std.c: was missing darwin.kevent64_s ziglang/zig#22632 (macos)
• std.c: was missing more ziglang/zig#22634 (macos)
• std: mkdir(2) mode uses mode_t ziglang/zig#22641 (all)
• std.c: define more fields for darwin.AI ziglang/zig#22652 (macos)
• std.c: more fixes ziglang/zig#22654 (macos + all)

Issues filed upstream (non-blocking):

• addition of try prevents proper error unwrapping coercion ziglang/zig#22633
• type 'T' has no members error has no 'defined here' notes ziglang/zig#22666
• cannot represent integer value error should have a 'defined here' note when its a parameter ziglang/zig#22670
• no decl literal completion in return statement zigtools/zls#2161
• no decl literal completion in block break zigtools/zls#2162

[robobun]

^{Updated 1:03 AM PT - Feb 1st, 2025}

❌ @nektro, your commit 4e840f7 has 1 failures in Build #10972:

• test/js/bun/util/filesink.test.ts - timeout on 🪟 2019 x64
• test/js/bun/util/filesink.test.ts - timeout on 🪟 2019 x64-baseline

---

🧪   try this PR locally:

bunx bun-pr 16862

[Jarred-Sumner]

it's clearer to keep it as the exact CSS property name. Instead of having to mentally ask "is it background-color or is it color?

[nektro]

i presumed that was clear since it was on BackgroundProperty and i needed the fields to not interfere with the decl shorthands which are used heavily and do match the name of the respective property

[paperclover]

what is the upgrade path for @fence?

after looking through them, i suspect most can be removed without additional changes. some need to change related atomic accesses (see ziglang/zig#21585)