Fixing the JEST config for IDEs

When using an IDE or an editor, those expect jest.config.js in the
project's root if nothing else is specificed in the config. In case of
two separate configs, we would need to update the configs for every jest
spec run that is not very enjoyable.

.eslintignore

@@ -9,6 +9,7 @@
 /scripts/
 /tmp/
 /vendor/
+jest.config.js
 jest.config.*.js
 karma.config.js
 webpack.config.js

package.json

@@ -10,7 +10,7 @@
     "eslint-report": "eslint --max-warnings 0 --ext .js,.vue --format html --output-file ./eslint-report.html --no-inline-config .",
     "file-coverage": "scripts/frontend/file_test_coverage.js",
     "prejest": "yarn check-dependencies",
-    "jest": "jest --config jest.config.unit.js",
+    "jest": "jest --config jest.config.js",
     "jest-debug": "node --inspect-brk node_modules/.bin/jest --runInBand",
     "jest:integration": "jest --config jest.config.integration.js",
     "jsdoc": "jsdoc -c config/jsdocs.config.js",

spec/frontend/.eslintrc.yml

@@ -10,7 +10,7 @@ settings:
     - path
   import/resolver:
     jest:
-      jestConfigFile: 'jest.config.unit.js'
+      jestConfigFile: 'jest.config.js'
 globals:
   getJSONFixture: false
   loadFixtures: false