chore: migrate test runner from mocha to jest (#2567)

# Migrate Winston Test Suite from Mocha to Jest
This PR fully migrates Winston's test suite from Mocha to Jest to provide a more fully featured testing framework

> [!WARNING]
> The File Transport tests while passing in their current form, illustrate in my opinion 
 some potential issues in how it currently functions.
>  - You can see the `FIX:` comments on a couple of assertions that I presume are correct but are currently failing. 
>  - The intersection of behavior with with the `maxsize` and `lazy` options result in behavior I found unexpected. e.g. If the rotation is not lazy, it will drop a log file resulting in 1 less populated log file than I would expect
>  - The maxsize option appears not to be strictly enforced on a per-file basis. This is probably desirable as in maxsize is likely on a best effort basis. I make this presumption given we wouldn't want to split a log payload across two files, nor do I think we should truncate it. The documentation for the Transport does not state either way though so look to someone with more familiarity than I about original intent.d

## Summary
- Refactored failing tests to be Jest-compatible
  - Primarily this was just modify `before()`, `after()`, `this.timeout()` to `beforeAll()`, `afterAll()`, and `jest.setTimeout()`
- Moved the `winston.test.js` from `integration` to `unit`. This felt more appropriate given the contents of the test.
- Refactored some tests for clarity or to resolve testing framework incompatabilities
  - Jest intercepts all stderr and pipes to stdout, so some tests have been updated to rely on Spies of `console.error`
  - Introduce async/await in some tests to reduce function nesting.
  - Combine File Archive tests and remove tests that I felt were redundant. This ensures these tests run sequentially as they're in the same file. This helps to avoid the potential of race conditions. Further improvements could likely be made here. Lastly these are not what I would label as unit tests and would likely advocate moving them to the `integration` suite given they're actually writing files to the FS.

## Test Plan
- All tests are passing in CI environment
- Manual verification of test coverage shows equivalent or better coverage compared to Mocha
- Verified file system tests properly clean up temporary files
- Confirmed logging tests produce expected output formats

Author: maverick1872

.eslintrc

@@ -1,4 +1,7 @@
 {
+  "env": {
+    "jest": true,
+  },
   "extends": "@dabh/eslint-config-populist",
   "rules": {
     "one-var": ["error", { "var": "never", "let": "never", "const": "never" }],

.github/workflows/ci.yml

@@ -21,6 +21,7 @@ jobs:
 
     runs-on: ubuntu-latest
     strategy:
+      fail-fast: false
       matrix:
         node:
           - 16
@@ -31,18 +32,24 @@ jobs:
       - uses: actions/setup-node@v4
         with:
           node-version: ${{ matrix.node }}
+
       - name: Install Dependencies
         run: npm clean-install
+
       - name: Lint
         run: npm run lint
+
+      - name: Unit Tests (with coverage)
+        run: npm run test:unit
+
       - name: Integration Tests
         run: npm run test:integration
-      - name: Test Coverage
-        run: npm run test:coverage
+
       - name: Report test coverage to Coveralls.io
         if: matrix.node == '20'
         uses: coverallsapp/github-action@master
         with:
           github-token: ${{ secrets.GITHUB_TOKEN }}
+
       - name: TypeScript Test
-        run: npx --package typescript tsc --project test
+        run: npm run test:typescript

.mocharc.yml

@@ -1234,15 +1234,17 @@ yarn add winston
 
 ## Run Tests
 
-All of the winston tests are written with [`mocha`][mocha], [`nyc`][nyc], and
-[`assume`][assume].  They can be run with `npm`.
-
 ``` bash
-npm test
+npm test # Runs all tests
+npm run test:unit # Runs all Unit tests with coverage
+npm run test:integration # Runs all integration tests
+npm run test:typescript # Runs tests verifying Typescript types
 ```
 
+All of the winston tests are written with [jest]. Assertions use a mix of [assume] and the built-in jest assertion library.
+
 #### Author: [Charlie Robbins]
-#### Contributors: [Jarrett Cruger], [David Hyde], [Chris Alderson]
+#### Contributors: [Jarrett Cruger], [David Hyde], [Chris Alderson], [Jonathon Terry]
 
 [Transports]: #transports
 [Logging levels]: #logging-levels
@@ -1254,11 +1256,10 @@ npm test
 
 [RFC5424]: https://tools.ietf.org/html/rfc5424
 [util.format]: https://nodejs.org/dist/latest/docs/api/util.html#util_util_format_format_args
-[mocha]: https://mochajs.org
-[nyc]: https://github.com/istanbuljs/nyc
 [assume]: https://github.com/bigpipe/assume
 [logform]: https://github.com/winstonjs/logform#readme
 [winston-transport]: https://github.com/winstonjs/winston-transport
+[jest]: https://jestjs.io/
 
 [Read the `[email protected]` documentation]: https://github.com/winstonjs/winston/tree/2.x
 
@@ -1268,4 +1269,5 @@ npm test
 [Charlie Robbins]: https://github.com/indexzero
 [Jarrett Cruger]: https://github.com/jcrugzz
 [David Hyde]: https://github.com/dabh
-[Chris Alderson]: https://github.com/chrisalderson
+[Chris Alderson]: https://github.com/chrisalderson
+[Jonathon Terry]: https://github.com/maverick1872

.nycrc.yml

@@ -0,0 +1,26 @@
+/**
+ * @type {import('@jest/types').Config.InitialOptions}
+ */
+module.exports = {
+  collectCoverage: false,
+  collectCoverageFrom: [
+    '<rootDir>/lib/**/*.js'
+  ],
+  coverageDirectory: 'coverage',
+  testEnvironment: 'node',
+  testMatch: [
+    '<rootDir>/test/**/*.test.js'
+  ],
+  globalSetup: '<rootDir>/test/globalSetup.js',
+  silent: true,
+  verbose: true,
+  coverageThreshold: {
+    global: {
+      functions: 74.54,
+      lines: 72.48,
+      statements: 72.25,
+      branches: 64.04
+    }
+  }
+};
+

README.md

@@ -48,6 +48,6 @@ class Profiler {
 
     return this.logger.write(info);
   }
-};
+}
 
 module.exports = Profiler;