update compat-data related docs/config [skip ci] (#11030)

* ignore compat-data build

* ignore CONTRIBUTING.md when publishing preset-env

* docs: update preset-env CONTRIBUTING.md

.eslintignore

@@ -17,9 +17,9 @@ codemods/*/lib
 codemods/*/dist
 codemods/*/test/fixtures
 codemods/*/test/tmp
+packages/babel-compat-data/build
 packages/babel-preset-env/data/[^(plugin-features|shipped-proposals).js]
 packages/babel-preset-env/test/debug-fixtures
-packages/babel-preset-env/build
 packages/babel-preset-env-standalone/babel-preset-env.js
 packages/babel-preset-env-standalone/babel-preset-env.min.js
 packages/babel-standalone/babel.js

packages/babel-preset-env/.npmignore

@@ -16,3 +16,4 @@ flow-typed
 .github
 .idea
 /build
+CONTRIBUTING.md

packages/babel-preset-env/CONTRIBUTING.md

@@ -63,25 +63,16 @@ If you want to mark a new proposal as shipped, add it to [this list](https://git
 
 ### Update [`plugins.json`](https://github.com/babel/babel/blob/master/packages/babel-preset-env/data/plugins.json)
 
-Until `compat-table` is a standalone npm module for data we are using the git commit in `scripts/download-compat-table.sh`
+Until `compat-table` is a standalone npm module for data we are using the git commit in `packages/babel-compat-data/scripts/download-compat-table.sh`
 
 `COMPAT_TABLE_COMMIT=[latest-commit-hash]`,
 
 So we update and then run `npm run build-data`. If there are no changes, then `plugins.json` will be the same.
 
 ## Tests
 
-### Running tests locally
-
-```bash
-npm test
-```
-
-### Checking code coverage locally
-
-```bash
-npm run coverage
-```
+### Running tests
+See general [CONTRIBUTING.md](https://github.com/babel/babel/blob/master/CONTRIBUTING.md#running-lintingtests).
 
 ### Writing tests