Description

Closes #15407.

It should give very good defaults with the related proposal #15890 which provides defaults for file pattern matching.

Describe the bug

Running the JS linter will lint the build/ folder, resulting in hundreds of errors because it's minified, etc.
When using wp-scripts to build blocks or other plugins that use wp.element, wp.component, etc. For example.>
Expected behavior

The build/ folder should be ignored by the linter config.

This PR ensures that by default all files located in build and node_modules folders are ignored when using wp-scripts for all 3 types of linter:

• lint-js
• lint-pkg-json
• lint-style

How has this been tested?

This is quite difficult to test without publishing to npm. I personally tested it with Gutenberg repository by playing with configuration files. This is how you can run commands:

• npx wp-scripts lint-js .
• npx wp-scripts lint-pkg-json .
• npx wp-scripts lint-style '**/*.scss'

I deleted .eslintignore from the root folder of Gutenberg and played with defaults:

• packages/scripts/config/.eslintignore
• packages/scripts/config/.npmpackagejsonlintignore
• packages/scripts/config/.stylelintignore

I had to add some linting errors in random files to ensure it all works.

Then I reverted changes in those config files and copied them to the root folder. I tried again to modify those config files in the root folder running all commands again.

I also ensured that when I add violations to files inside build or node_modules nested subfolder, those errors are ignored.