Lukas 'Eipi' Eipert 创作于 4 years ago ，Vitaly Slobodin 提交于 4 years ago

This re-adds our config/, scripts/ and *.config.js files to eslint,
together with some rules to make it a little easier for those
node-scripts, e.g. console logging or importing node or dev dependencies
should be fine.

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.

**Why?**
To write [FE integration tests][1], we will need
to have two related but different environments.
The best way to do this is with two configs and
a base config.

[1]: https://docs.gitlab.com/ee/development/testing_guide/testing_levels.html#frontend-integration-tests

(cherry picked from commit 5a2d7bf2)

- Re-enable stateStorageStrategy=localStorage
- Move snowplow to vendor directory
- Cleanup .eslintignore
- Fix test

Add the following line to GDK Procfile to play with it:

    webpack: exec support/exec-cd gitlab npm run dev-server

Change airbnb eslint config package to `eslint-config-airbnb-base` and update plugins.

Change `airbnb` to `airbnb-base` for .eslintrc `extends` value.

Added changelog entry

Made sure all plugins and envs are set

Corrected new failing specs

ESLint config: https://github.com/airbnb/javascript