fix: resolve cargo-fuzz rustix breakage and babel cache conflict

- Install cargo-fuzz from git main instead of crates.io: v0.13.1 is the
  latest release and still pins rustix-0.36.5, which nightly Rust now
  rejects because it uses rustc_layout_scalar_valid_range_* attributes
  inside cfg_attr — the git version has updated its cargo dependency
  to one that uses rustix 0.38.x where those attributes were removed
- Fix babel.config.js: api.cache(true) locks caching to forever mode
  and api.env() then throws "Caching has already been configured with
  .never or .forever()". Replace api.env('production') with a direct
  process.env.NODE_ENV read which bypasses Babel's cache API entirely

Author: sweetesty

.github/workflows/fuzz-test.yml

@@ -43,7 +43,7 @@ jobs:
           components: llvm-tools
 
       - name: Install cargo-fuzz
-        run: cargo install cargo-fuzz --locked
+        run: cargo install --git https://github.com/rust-fuzz/cargo-fuzz cargo-fuzz
 
       - name: Restore seed corpus from cache
         uses: actions/cache@v4

babel.config.js

@@ -1,6 +1,6 @@
 module.exports = function (api) {
   api.cache(true);
-  const isProduction = api.env('production');
+  const isProduction = process.env.NODE_ENV === 'production';
 
   const plugins = [
     [