Remove the node-file-trace crate (#70998)

### What?

This is a 2nd prefactor for adding node-file-trace into turbopack. When implementing this, we have a few options namely:

- a) expose turbotrace (node-file-trace-rs) as a napi library and try to insert it into the current codebase
- b) expose turbotrace and try to reuse the turbo backend
- c) move turobtrace into the rust process and do it in parallel with everything else

We chose c

We have already ripped out the js code path, this PR nukes the now-orphaned node-file-trace rust binary and napi bindings.

### Why?

The crate is unmaintained and probably will not be used in its current form.

Cargo.toml

@@ -40,7 +40,6 @@ next-custom-transforms = { path = "crates/next-custom-transforms" }
 
 # Turbopack
 auto-hash-map = { path = "turbopack/crates/turbo-tasks-auto-hash-map" }
-node-file-trace = { path = "turbopack/crates/node-file-trace", default-features = false }
 swc-ast-explorer = { path = "turbopack/crates/turbopack-swc-ast-explorer" }
 turbo-prehash = { path = "turbopack/crates/turbo-prehash" }
 turbo-tasks-malloc = { path = "turbopack/crates/turbo-tasks-malloc", default-features = false }

crates/napi/Cargo.toml

@@ -111,7 +111,6 @@ next-api = { workspace = true }
 next-build = { workspace = true }
 next-core = { workspace = true }
 
-node-file-trace = { workspace = true, features = ["node-api"] }
 mdxjs = { workspace = true, features = ["serializable"] }
 
 turbo-tasks-malloc = { workspace = true, default-features = false, features = [

crates/napi/src/lib.rs

@@ -60,8 +60,6 @@ pub mod transform;
 pub mod turbo_trace_server;
 #[cfg(not(target_arch = "wasm32"))]
 pub mod turbopack;
-#[cfg(not(target_arch = "wasm32"))]
-pub mod turbotrace;
 pub mod util;
 
 // Declare build-time information variables generated in build.rs