[chore] Upgrade ESLint (#499)

# Why

I've been having issues with VS Code complaining rules for `@typescript-eslint/no-throw-literal` and `.../ban-types` were missing.

# How

I've decided to try upgrading ESLint config. So far so good.

# Test Plan

CI should be green.

package.json

@@ -16,10 +16,10 @@
   },
   "devDependencies": {
     "@types/node": "20.14.2",
-    "eslint": "8.56.0",
-    "eslint-config-universe": "13.0.0",
-    "eslint-plugin-import": "2.29.1",
-    "eslint-plugin-jest": "28.6.0",
+    "eslint": "^8.57.1",
+    "eslint-config-universe": "14.0.0",
+    "eslint-plugin-import": "2.31.0",
+    "eslint-plugin-jest": "28.11.0",
     "lerna": "^7.1.4",
     "prettier": "3.3.1",
     "typescript": "5.4.5"

packages/steps/src/__tests__/BuildStep-test.ts

@@ -521,7 +521,7 @@ describe(BuildStep, () => {
           ],
           command,
         });
-        const error = await getErrorAsync<BuildStepRuntimeError>(async () => step.executeAsync());
+        const error = await getErrorAsync<BuildStepRuntimeError>(() => step.executeAsync());
         expect(error).toBeInstanceOf(BuildStepRuntimeError);
         expect(error.message).toMatch(/Some required outputs have not been set: "abc"/);
       });