next.js

3b53dce4 - Make Firebase tracing fixture independent of backend connectivity (#101180)

Make Firebase tracing fixture independent of backend connectivity (#101180) ## Summary The Firebase node-file-trace fixture currently contacts Firestore, so different backend connection failures can produce different stderr in the original and traced executions and fail cargo unit tests. Disable networking before the query and assert an empty, cache-derived result. This retains the real SDK and its runtime gRPC/protobuf loading without requiring a live backend, mock server, or new dependencies. Clean up the Firebase client before exiting. ## Verification - Both focused Cargo tracing cases pass with socket connections and DNS resolution blocked, using the CI profile and locked Firebase dependencies. - Instrumentation confirms that original and emitted fixtures still load the real Firestore protobuf definitions. - Repeated offline runs and injected query/assertion failures behave as expected. <!-- NEXT_JS_LLM --> <!-- fleet a0d936ce-cfed-498f-8758-fb469a153b09 --> --------- Co-authored-by: vercel-fleet-prod[bot] <318278635+vercel-fleet-prod[bot]@users.noreply.github.com> Co-authored-by: Will Binns-Smith <755844+wbinnssmith@users.noreply.github.com>