Bump jest from 28.1.3 to 29.0.2, jest-preset-stylelint from 5.0.4 to …

…6.0.0 (#6332)

* Bump jest from 28.1.3 to 29.0.2, jest-preset-stylelint from 5.0.4 to 6.0.0

* Bump eslint from 8.25.0 to 8.26.0 (#6422)

Bumps [eslint](https://github.com/eslint/eslint) from 8.25.0 to 8.26.0.
- [Release notes](https://github.com/eslint/eslint/releases)
- [Changelog](https://github.com/eslint/eslint/blob/main/CHANGELOG.md)
- [Commits](eslint/eslint@v8.25.0...v8.26.0)

---
updated-dependencies:
- dependency-name: eslint
  dependency-type: direct:development
  update-type: version-update:semver-minor
...

* Update snapshots with `npm run jest -- -u`

Co-authored-by: Richard Hallows <jeddy3@users.noreply.github.com>

lib/__tests__/__snapshots__/cli.test.js.snap

@@ -29,8 +29,8 @@ exports[`CLI --help 1`] = `
 
     --config-basedir
 
-      An absolute path to the directory that relative paths defining \\"extends\\"
-      and \\"plugins\\" are *relative to*. Only necessary if these values are
+      An absolute path to the directory that relative paths defining "extends"
+      and "plugins" are *relative to*. Only necessary if these values are
       relative paths.
 
     --print-config
@@ -76,31 +76,31 @@ exports[`CLI --help 1`] = `
 
       Store the info about processed files in order to only operate on the
       changed ones the next time you run stylelint. By default, the cache
-      is stored in \\"./.stylelintcache\\". To adjust this, use --cache-location.
+      is stored in "./.stylelintcache". To adjust this, use --cache-location.
 
     --cache-location              [default: '.stylelintcache']
 
       Path to a file or directory to be used for the cache location.
-      Default is \\"./.stylelintcache\\". If a directory is specified, a cache
+      Default is "./.stylelintcache". If a directory is specified, a cache
       file will be created inside the specified folder, with a name derived
       from a hash of the current working directory.
 
-      If the directory for the cache does not exist, make sure you add a trailing \\"/\\"
-      on *nix systems or \\"\\\\\\" on Windows. Otherwise the path will be assumed to be a file.
+      If the directory for the cache does not exist, make sure you add a trailing "/"
+      on *nix systems or "\\" on Windows. Otherwise the path will be assumed to be a file.
 
-    --cache-strategy              [default: \\"metadata\\"]
+    --cache-strategy              [default: "metadata"]
 
       Strategy for the cache to use for detecting changed files. Can be either
-      \\"metadata\\" or \\"content\\".
+      "metadata" or "content".
 
-      The \\"content\\" strategy can be useful in cases where the modification time of
+      The "content" strategy can be useful in cases where the modification time of
       your files changes even if their contents have not. For example, this can happen
-      during git operations like \\"git clone\\" because git does not track file modification
+      during git operations like "git clone" because git does not track file modification
       time.
 
-    --formatter, -f               [default: \\"string\\"]
+    --formatter, -f               [default: "string"]
 
-      The output formatter: \\"compact\\", \\"github\\", \\"json\\", \\"string\\", \\"tap\\", \\"unix\\" or \\"verbose\\".
+      The output formatter: "compact", "github", "json", "string", "tap", "unix" or "verbose".
 
     --custom-formatter
 
@@ -109,8 +109,8 @@ exports[`CLI --help 1`] = `
 
     --quiet, -q
 
-      Only register problems for rules with an \\"error\\"-level severity (ignore
-      \\"warning\\"-level).
+      Only register problems for rules with an "error"-level severity (ignore
+      "warning"-level).
 
     --color
     --no-color
@@ -135,7 +135,7 @@ exports[`CLI --help 1`] = `
     --max-warnings, --mw
 
       Number of warnings above which the process will exit with code 2.
-      Useful when setting \\"defaultSeverity\\" to \\"warning\\" and expecting the
+      Useful when setting "defaultSeverity" to "warning" and expecting the
       process to fail on warnings (e.g. CI build).
 
     --output-file, -o

lib/__tests__/applyOverrides.test.js

@@ -273,7 +273,7 @@ test('overrides is not an array', () => {
 	expect(() => {
 		applyOverrides(config, __dirname, path.join(__dirname, 'style.module.css'));
 	}).toThrowErrorMatchingInlineSnapshot(
-		`"The \`overrides\` configuration property should be an array, e.g. { \\"overrides\\": [{ \\"files\\": \\"*.css\\", \\"rules\\": {} }] }."`,
+		`"The \`overrides\` configuration property should be an array, e.g. { "overrides": [{ "files": "*.css", "rules": {} }] }."`,
 	);
 });
 
@@ -294,7 +294,7 @@ test('`files` is missing', () => {
 	expect(() => {
 		applyOverrides(config, __dirname, path.join(__dirname, 'style.module.css'));
 	}).toThrowErrorMatchingInlineSnapshot(
-		`"Every object in the \`overrides\` configuration property should have a \`files\` property with globs, e.g. { \\"overrides\\": [{ \\"files\\": \\"*.css\\", \\"rules\\": {} }] }."`,
+		`"Every object in the \`overrides\` configuration property should have a \`files\` property with globs, e.g. { "overrides": [{ "files": "*.css", "rules": {} }] }."`,
 	);
 });