test: explicitly require ts-node/register from both mocharcs

Mocha 10.5+ takes an ESM import() path for .ts spec files on some
Node versions (observed failing on Node 16 with mocha 10.8.2,
ERR_UNKNOWN_FILE_EXTENSION). The ESM path bypasses ts-node/register
which was previously only loaded via nyc.config.js — that only
patches require(), not import().

Adding `require: ['ts-node/register']` to both mocharcs forces mocha
to require the ts-node hook before resolving any specs, which keeps
the CJS loader path active for .ts files regardless of which Node
version is in use.

No impact on published package — tests/ is excluded by .npmignore.

Co-authored-by: Isaac
Signed-off-by: Vikrant Puppala <vikrant.puppala@databricks.com>

Author: vikrantpuppala

tests/e2e/.mocharc.js

@@ -7,4 +7,7 @@ const argvSpecs = process.argv.slice(4);
 module.exports = {
   spec: argvSpecs.length > 0 ? argvSpecs : allSpecs,
   timeout: '300000',
+  // Force the CommonJS loader path so .ts specs go through ts-node's
+  // require hook. See tests/unit/.mocharc.js for context.
+  require: ['ts-node/register'],
 };

tests/unit/.mocharc.js

@@ -6,4 +6,10 @@ const argvSpecs = process.argv.slice(4);
 
 module.exports = {
   spec: argvSpecs.length > 0 ? argvSpecs : allSpecs,
+  // Force the CommonJS loader path so .ts specs go through ts-node's
+  // require hook. Mocha 10.5+ otherwise picks the ESM import() path
+  // for .ts files on some Node versions, which bypasses
+  // ts-node/register (set in nyc.config.js) and fails with
+  // ERR_UNKNOWN_FILE_EXTENSION.
+  require: ['ts-node/register'],
 };