use node: prefix for requires

mostly because code is being autogenerated by all the AI stuff using
this prefix. it's also used in the stack trace.

src/backupformat/tgz.js

@@ -1,23 +1,23 @@
 'use strict';
 
-const assert = require('assert'),
+const assert = require('node:assert'),
     backupTargets = require('../backuptargets.js'),
     BoxError = require('../boxerror.js'),
-    crypto = require('crypto'),
+    crypto = require('node:crypto'),
     DataLayout = require('../datalayout.js'),
     debug = require('debug')('box:backupformat/tgz'),
     { DecryptStream, EncryptStream } = require('../hush.js'),
-    fs = require('fs'),
+    fs = require('node:fs'),
     HashStream = require('../hash-stream.js'),
-    path = require('path'),
+    path = require('node:path'),
     ProgressStream = require('../progress-stream.js'),
     promiseRetry = require('../promise-retry.js'),
-    { Readable } = require('stream'),
+    { Readable } = require('node:stream'),
     safe = require('safetydance'),
     stream = require('stream/promises'),
     { Transform } = require('node:stream'),
     tar = require('tar-stream'),
-    zlib = require('zlib');
+    zlib = require('node:zlib');
 
 // In tar, the entry header contains the file size. If we don't provide it those many bytes, the tar will become corrupt
 // Linux provides no guarantee of how many bytes can be read from a file. This is the case with sqlite and log files