Let's stay away from recommending `re.prefixmatch`.

[mbyrnepr2]

Current problem

This issue is to prevent a feature that adds a Pylint check to recommend re.prefixmatch instead of re.match.

The reason is that there have been some concerns expressed by the Python community that there could potentially be a time sink as a result of pull requests getting created in projects to change occurrences of re.match to re.prefixmatch.

A further concern from the community is that linters will begin to drive that time sink by adding recommendations to make those code changes.

Desired solution

Let's not add such a Pylint check and, if a feature request is made for adding it, we can point to this issue for the context and rationale.

Additional context

https://discuss.python.org/t/add-re-prefixmatch-deprecate-re-match/105927

[Pierre-Sassoulas]

I saw the same discussion and thought to myself, "we should add a check that warn when someone add a useless ^ at the beginning of a re.match call". (Similar to bad-str-strip-call, in spirit, right ? Code work, but it shows someone doesn't have full understanding of the function used.)