Add ESLint rule to error on problematic language

[sarayourfriend]

In order to avoid introducing new instances of problematic language.

To accomplish this we could use the id-blacklist rule. While as of today it is woefully (and in this case quite ironically) named, the ESLint project is undergoing the same process as us in removing this kind of problematic language: eslint/eslint#13407

We could either (a) go ahead and add it using the current id-blacklist named rule or (b) wait until ESLint have updated it, upgrade our dependency and then use the newly renamed rule. Either way, we should keep our eyes on eslint/eslint#13408, once it is merged and a new ESLint release is cut we can do the upgrade.

As far as the list of terms to add to the rule configuration, I think we could start with the following:

1. "whitelist"
2. "blacklist"
3. "master"
4. "slave"

[sarayourfriend]

There's actually already a project that does this: https://github.com/muenzpraeger/eslint-plugin-inclusive-language

The advantage to using that project is that it also provides helpful suggestions for alternatives, making maintenance around the issue as easy as possible 😁