test: remove internal errorCache property

The internal `assert` modules `errorCache` property is exposed only for
testing. The one test that used it is rewritten here to not use it.

This has the following advantages:

* The test now makes sure that there is an empty cache in a more robust
  way. Instead of relying on the internal implementation of
  `errorCache`, it simply spawns a separate process.
* One less test using the `--expose-internals` flag.

PR-URL: nodejs#23304
Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
Reviewed-By: Sakthipriyan Vairamani <thechargingvolcano@gmail.com>

Author: Trott

test/parallel/test-assert-builtins-not-read-from-filesystem.js

@@ -19,13 +19,13 @@ if (process.argv[2] !== 'child') {
     e.emit('hello', false);
   } catch (err) {
     const frames = err.stack.split('\n');
-    const [, filename, line, column] = frames[1].match(/\((.+):(\d+):(\d+)\)/);
+    const [, filename, , ] = frames[1].match(/\((.+):(\d+):(\d+)\)/);
     // Spawn a child process to avoid the error having been cached in the assert
     // module's `errorCache` Map.
 
     const { output, status, error } =
       spawnSync(process.execPath,
-                [process.argv[1], 'child', filename, line, column],
+                [process.argv[1], 'child', filename],
                 { cwd: tmpdir.path, env: process.env });
     assert.ifError(error);
     assert.strictEqual(status, 0, `Exit code: ${status}\n${output}`);