chore: update to Rust 1.74

[aqrln]

https://blog.rust-lang.org/2023/11/16/Rust-1.74.0.html

Changes in this commit:

• Update Nix flake, including nixpkgs and rust-overlay:

  • Rust 1.74
  • Node.js 21.1.0
  • wasm-bindgen 0.2.88
  • etc

• Bump wasm-bindgen dependency in Cargo.toml to match the new
  version of external wasm-bindgen binary installed on CI via Nix.
  Their versions must always match for the build to succeed.

• Fix the clippy warnings.

[aqrln]

crane doesn't depend on these anymore

[codspeed-hq]

CodSpeed Performance Report

Merging #4461 will not alter performance

_{Comparing chore-update-to-rust-1.74 (b7f0918) with main (800a9b4)}

Summary

✅ 11 untouched benchmarks

[Jolg42]

@aqrln Technically, that's mostly an update of https://github.com/ipetkov/crane? To which version? It's not obvious to me to find the version in https://github.com/ipetkov/crane/releases

[aqrln]

@Jolg42

Technically, that's mostly an update of https://github.com/ipetkov/crane?

No, on the Nix side it's primarily an update of nixpkgs and rust-overlay, but crane is updated along the way too.

To which version?

To the latest commit, we are not currently locked to any specific tag.

[Jolg42]

Looks good to me.

I unlocked the release pipeline in https://buildkite.com/prisma/test-prisma-engines/builds/21627
Could you first check if both the test and release pipelines are passing before merging?

[miguelff]

I'm not qualified to asess nix changes are correct, but Rust is good.

[aqrln]

@Jolg42

Could you first check if both the test and release pipelines are passing before merging?

Sure, but it doesn't really matter, our Docker images used on Buildkite are updated independently and these changes have no influence on them. Nix is only used in the release process of prisma-schema-wasm right now.

It's a problem on its own by the way because they often end up lagging several minor versions behind until we use something that doesn't compile with old Rust anymore and remember to rebuild them, and when rebuilding those images we have no way to automatically test them before rolling them out to be used in CI.