gh-138186: Use 'predicate' instead of 'function' in filterfalse docstring

[kovan]

Summary

• Changes the parameter name in itertools.filterfalse's docstring from function to predicate
• This makes it consistent with:
  • The RST documentation (Doc/library/itertools.rst) which already uses predicate
  • The similar functions dropwhile and takewhile which use predicate

Before:

>>> help(itertools.filterfalse)
filterfalse(function, iterable, /)

After:

>>> help(itertools.filterfalse)
filterfalse(predicate, iterable, /)

Test plan

• make check passed

🤖 Generated with Claude Code

• Issue: The doc of itertools.filterfalse() shows predicate argument but the docstring shows function argument #138186

[bedevere-app]

Most changes to Python require a NEWS entry. Add one using the blurb_it web app or the blurb command-line tool.

If this change has little impact on Python users, wait for a maintainer to apply the skip news label instead.

[picnixz]

It's not about dropwhile/takewhile, but about filter/filterfalse. See #138186 (comment). And again, read the issue before opening PRs. IMO, semantically, predicate is more correct but at runtime, we don't require the predicate to return a boolean as we use truthiness (predicates should really be boolean functions).

[bedevere-app]

A Python core developer has requested some changes be made to your pull request before we can consider merging it. If you could please address their requests along with any other requests in other reviews from core developers that would be appreciated.

Once you have made the requested changes, please leave a comment on this pull request containing the phrase I have made the requested changes; please review again. I will then notify any core developers who have left a review that you're ready for them to take another look at this pull request.

[picnixz]

Since we still haven't reached a consensus on the issue, I'm closing it for now.