Remove /wordpress from test/linting ignore paths

[johnwatkins0]

Description

This resolves #20255 by removing /wordpress where it appears among linting/testing ignore patterns, essentially undoing everything in https://github.com/WordPress/gutenberg/pull/17296/files.

Having /wordpress/ in the ignore patterns was preventing Jest tests from being recognized when the project has /wordpress/ somewhere in the system directory path. According to @talldan
in #20255 (comment), the original reason for ignoring the directory no longer applies, so it can be removed.

How has this been tested?

Ran linting and tests locally after the change. Everything worked.

Screenshots

Types of changes

Change to test and linting configurations.

Checklist:

• My code is tested.
• My code follows the WordPress code style.
• My code follows the accessibility standards.
• My code has proper inline documentation.
• I've included developer documentation if appropriate.
• I've updated all React Native files affected by any refactorings/renamings in this PR.

[talldan]

Thanks for following up on this @johnwatkins0.

Perhaps the wordpress folder should also be removed from the .gitignore file now that it's not expected to be there. What do you think?

[johnwatkins0]

Thanks, @talldan. I agree -- if there's no longer anything in plugin development process that creates a /wordpress directory, it doesn't need to be in .gitignore. I've updated.

[gziolo]

Thank you for working on it. We should deprecate wp-scripts env first, before we land this PR. It is still referenced in some places in the root package.json of Gutenberg . In addition, if someone uses @wordpress/scripts and they run env script, they will see unexpected errors.

[talldan]

We should deprecate wp-scripts env first

@gziolo Ah, does that still install wordpress into a local folder? I didn't realise that.

It looks like the older env is still used for travis, so that'd be one of the first places to replace with the newer wp-env:

gutenberg/.travis.yml

Lines 83 to 99 in c76137b

	npm run env:start
	sleep 10
	npm run env:install
	cd ..
	# Connect Gutenberg to WordPress.
	npm run env connect
	npm run env cli plugin activate gutenberg
	fi
	- |
	if [[ "$INSTALL_COMPOSER" = "true" ]]; then
	npm run env docker-run -- php composer install
	fi
	- |
	if [[ "$E2E_ROLE" = "author" ]]; then
	npm run env cli -- user create author [email protected] --role=author --user_pass=authpass
	npm run env cli -- post update 1 --post_author=2

[gziolo]

@gziolo Ah, does that still install wordpress into a local folder? I didn't realise that.

It probably does. At least, it's what happens locally :)

[gziolo]

@johnwatkins0, we can land this changes now tfst @wordpress/env is widely used. Would you mind bringing this PR up to date?

There is also a note about ignored wordpress folder in README file of @wordpress/scripts package.

[johnwatkins0]

There is also a note about ignored wordpress folder in README file of @wordpress/scripts package.

@gziolo This PR has been updated, and the README file was modified in 0fdb93a

[gziolo]

Thank you 👍