Cardano Updates

Changes:
- Updated node_modules derivation to use -Wno-error instead of
  -Wno-enum-constexpr-conversion for npm_config_cxxflags
- Updated daedalus derivation to match
- Updated rebuild-native-modules.sh script to export the flag with multiple
  variations for compatibility

The -Wno-enum-constexpr-conversion flag is not supported by older clang
versions in nixpkgs-22.11 (used for aarch64-darwin native builds). Using
-Wno-error makes all warnings non-fatal and works across all clang versions,
fixing blake-hash compilation errors.

This fix applies to:
- x86_64-darwin (cross-compiled on aarch64)
- aarch64-darwin (native builds)

Fixes the enum constexpr conversion error in node-addon-api header that
occurs when compiling native Node.js modules with newer clang that enforces
stricter enum type checking.

Add explicit export of npm_config_cxxflags before electron-rebuild calls to
ensure the -Wno-enum-constexpr-conversion flag is passed to node-gyp. This
fixes blake-hash compilation errors on aarch64-darwin with newer clang that
rejects enum constexpr conversions.

Previously, npm_config_cxxflags was only set as a derivation attribute but not
explicitly exported in the buildPhase script. This caused electron-rebuild on
native aarch64-darwin builds to not pick up the -Wno-enum-constexpr-conversion
flag, resulting in blake-hash compilation errors.

The export now ensures both x86_64-darwin cross-compilation and native
aarch64-darwin builds properly pass the flag to node-gyp/electron-rebuild.

Add -Wno-enum-constexpr-conversion flag to allow blake-hash and other
native modules to compile when cross-compiling x86_64-darwin on Apple
Silicon builders. The node-addon-api uses -1 as a sentinel enum value
which newer clang versions reject as invalid.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <[email protected]>

Signed-off-by: Chris Gianelloni <[email protected]>

Use pkgsJs.stdenv.mkDerivation instead of pkgs.stdenv.mkDerivation for
the node_modules derivation on Darwin. This ensures the entire build
environment (compiler, linker, and build tools) comes from nixpkgs-22.11,
avoiding both clang enum compatibility issues and linker errors with
native node modules.

Also consolidate darwin.cctools, xcbuild, and python3 to use pkgsJs for
consistency.

Use pkgsJs (nixpkgs-22.11) instead of pkgs (nixpkgs-25.11) for:
- Darwin: darwin.cctools, xcbuild, python3 to avoid clang compatibility
  issues with node-addon-api (enum value -1 error)
- Windows: haskell.lib.justStaticExecutables to avoid disallowGhcReference
  argument incompatibility in Haskell generic-builder

These components require the older toolchain from nixpkgs-22.11 to build
successfully after the nixpkgs-25.11 upgrade.

GHC 8.10.7 (ghc8107) was removed in nixpkgs-25.11, so the Windows
installer build needs to use pkgsJs (nixpkgs-22.11) where it still exists.

GHC 8.10.7 (ghc8107) was removed in nixpkgs-25.11, so the Windows
installer build needs to use pkgsJs (nixpkgs-22.11) where it still exists.

This error surfaced in the flake-parts branch because Windows installers
are now exposed in packages.x86_64-linux (for cross-compilation), which
causes eager evaluation. On the mithril branch, they were only in hydraJobs.

Signed-off-by: Chris Gianelloni <[email protected]>