Regenerate fixtures with node@24

Author: fvictorio

v-next/hardhat-node-test-reporter/integration-tests/fixture-tests/assert-test/result.svg

@@ -12,7 +12,7 @@
       8) should match strings
 
 
-  0 passing (153ms)
+  0 passing (161ms)
   8 failing
 
   1) assert

v-next/hardhat-node-test-reporter/integration-tests/fixture-tests/assert-test/result.txt

@@ -47,7 +47,7 @@
   8) describe.describe.async.it.only
 
 
-  12 passing (160ms)
+  12 passing (172ms)
   8 failing
 
   1) describe.async.describe.async.it:

v-next/hardhat-node-test-reporter/integration-tests/fixture-tests/async-describe-test/result.svg

@@ -1,10 +1,10 @@
 
   ✔ foo
 
-  1) integration-tests/fixture-tests/asynchronous-activity-test/test.ts (214ms)
+  1) integration-tests/fixture-tests/asynchronous-activity-test/test.ts (223ms)
 
 
-  1 passing (244ms)
+  1 passing (253ms)
   1 failing
   ℹ Error: Test "foo" at integration-tests/fixture-tests/asynchronous-activity-test/test.ts:1:29 generated asynchronous activity after the test ended. This activity created the error "Error" and would have caused the test to fail, but instead triggered an uncaughtException event.