Add support for recursiveDenylist option as an alternative to recursiveBlacklist

[wojtekmaj]

Summary

Clone of #10236 which has to be closed because the original repo was deleted by me.

Part of #10235.

• Adds support for recursiveDenylist option as an alternative to recursiveBlacklist in jest-validate. Does NOT remove recursiveBlacklist option. It will continue to work, unless overwritten with recursiveDenylist, to which I've given the priority.
• Updates documentation not to mention recursiveBlacklist (in favor of the newly added option).
• Changes internal calls to validate() to use new config (Maintainers: I'm not sure if that's a good idea - can you please advise? Should we expect jest-config, say, v26.2 work with other dependencies @ v26.1 at all times? Shall I roll that back and add it as a TODO to Replace non-inclusive terms used in configuration of jest-validate #10235 instead? TIA)

Motivation

Part of continuous effort to get rid of non-inclusive terms like "whitelist" and "blacklist" implying that white = good and black = bad.

Test plan

jest-validate had one suite where recursiveBlacklist option was used, in two cases:

• test the very recursiveBlacklist option
• test for warning against unknown config options

The former was left intact, and copied 1:1 over to create a new test, testing whether recursiveDenylist beaves exactly the same as recursiveBlacklist.

The latter was updated to use recursiveDenylist.

Tests were ran successfully.

[SimenB]

Thanks! Could you fix the linting errors in jest-validate/src/validate.ts?

[wojtekmaj]

I'm a complete idiot, I was so happy there are no errors, and turns out there were none because I forgot to install it 🙄

[SimenB]

Thanks @wojtekmaj! A PR which removes the old alias would be very much welcome, and I can land that when we start landing breaking changes 🙂 Just don't delete your fork so I can merge in master once I start landing 😀

[github-actions]

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.