Add regexs for bad- and good-names to enable better white- or blacklisting

[Germandrummer92]

Steps

• Add yourself to CONTRIBUTORS if you are a new contributor.
• Add a ChangeLog entry describing what your PR does.
• If it's a new feature or an important bug fix, add a What's New entry in doc/whatsnew/<current release.rst>.
• Write a good description on what the PR does.

Description

Adds two new config options: bad-names-rgxs and good-names-rgxs, to enable easier white/blacklisting of names.

Type of Changes

| ✓ | ✨ New feature |

Related Issue

Closes #3086

[coveralls]

Coverage increased (+0.01%) to 89.853% when pulling a238c75 on Germandrummer92:master into 86d2811 on PyCQA:master.

[PCManticore]

Hey @Germandrummer92

Thank you for your PR! Overall looks good, but there are some things to improve before getting this in.

[Germandrummer92]

Hey @Germandrummer92

Thank you for your PR! Overall looks good, but there are some things to improve before getting this in.

@PCManticore Fixed all your comments, thanks! I was wondering: I personally think the config keys whitelisted-names whitelisted-names-rgxs blacklisted-names blacklisted-names-rgxs would be both clearer and make the naming in the code easier than the current good/bad-names*. But it would obviously be a breaking change for people already using the old config keys. Any way we could introduce the newer ones and give a deprecation warning if people use the old one? Or do you think the current names are fine?

[PCManticore]

Hey @Germandrummer92 The current names are fine. While we could change them, we currently don't have a mechanism for deprecation of options like you mentioned (we do have for check messages though).

[PCManticore]

Thanks a lot for the PR! 😄