Improve output of consider-using-generator message for min() calls with default keyword

[jacobtylerwalls]

Type of Changes

	Type
✓	🐛 Bug fix

Description

Closes #8563

[codecov]

Codecov Report

Merging #8582 (aec217f) into main (2db55f6) will increase coverage by 0.00%.
The diff coverage is 100.00%.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #8582   +/-   ##
=======================================
  Coverage   95.91%   95.91%           
=======================================
  Files         174      174           
  Lines       18371    18394   +23     
=======================================
+ Hits        17620    17643   +23     
  Misses        751      751           

Impacted Files	Coverage Δ
pylint/checkers/refactoring/refactoring_checker.py	98.34% <100.00%> (+<0.01%)	⬆️

... and 2 files with indirect coverage changes

[Pierre-Sassoulas]

LGTM, should we backport this kind of bug fixes ?

[github-actions]

🤖 Effect of this PR on checked open source code: 🤖

Effect on django:
The following messages are now emitted:

1. consider-using-generator:
   Consider using a generator instead 'max((self.lastmod(item) for item in self.items()), default=None)'
   https://github.com/django/django/blob/255f5345904854128647705adcb8d21138e87c63/django/contrib/sitemaps/__init__.py#L162

The following messages are no longer emitted:

1. consider-using-generator:
   Consider using a generator instead 'max(self.lastmod(item) for item in self.items())'
   https://github.com/django/django/blob/255f5345904854128647705adcb8d21138e87c63/django/contrib/sitemaps/__init__.py#L162

This comment was generated for commit aec217f

[jacobtylerwalls]

LGTM, should we backport this kind of bug fixes ?

Why not.