Fix consider-using-min-max-builtin

[onlined]

Type of Changes

	Type
✓	🐛 Bug fix

Description

Fix a false positive for consider-using-min-max-builtin when the assignment target is an attribute.

Closes #9800

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 95.79%. Comparing base (47fb321) to head (f9330c5).
Report is 119 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #9802   +/-   ##
=======================================
  Coverage   95.78%   95.79%           
=======================================
  Files         174      174           
  Lines       18880    18902   +22     
=======================================
+ Hits        18085    18107   +22     
  Misses        795      795           

Files with missing lines	Coverage Δ
pylint/checkers/refactoring/refactoring_checker.py	98.15% <100.00%> (-0.01%)	⬇️

... and 1 file with indirect coverage changes

[github-actions]

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

Effect on django:
The following messages are now emitted:

1. consider-using-min-builtin:
   Consider using 'self._envelope.MinX = min(self._envelope.MinX, minx)' instead of unnecessary if block
   https://github.com/django/django/blob/082fe2b5a83571dec4aa97580af0fe8cf2a5214e/django/contrib/gis/gdal/envelope.py#L131
2. consider-using-min-builtin:
   Consider using 'self._envelope.MinY = min(self._envelope.MinY, miny)' instead of unnecessary if block
   https://github.com/django/django/blob/082fe2b5a83571dec4aa97580af0fe8cf2a5214e/django/contrib/gis/gdal/envelope.py#L133
3. consider-using-max-builtin:
   Consider using 'self._envelope.MaxX = max(self._envelope.MaxX, maxx)' instead of unnecessary if block
   https://github.com/django/django/blob/082fe2b5a83571dec4aa97580af0fe8cf2a5214e/django/contrib/gis/gdal/envelope.py#L135
4. consider-using-max-builtin:
   Consider using 'self._envelope.MaxY = max(self._envelope.MaxY, maxy)' instead of unnecessary if block
   https://github.com/django/django/blob/082fe2b5a83571dec4aa97580af0fe8cf2a5214e/django/contrib/gis/gdal/envelope.py#L137

The following messages are no longer emitted:

1. consider-using-min-builtin:
   Consider using 'MinX = min(MinX, minx)' instead of unnecessary if block
   https://github.com/django/django/blob/082fe2b5a83571dec4aa97580af0fe8cf2a5214e/django/contrib/gis/gdal/envelope.py#L131
2. consider-using-min-builtin:
   Consider using 'MinY = min(MinY, miny)' instead of unnecessary if block
   https://github.com/django/django/blob/082fe2b5a83571dec4aa97580af0fe8cf2a5214e/django/contrib/gis/gdal/envelope.py#L133
3. consider-using-max-builtin:
   Consider using 'MaxX = max(MaxX, maxx)' instead of unnecessary if block
   https://github.com/django/django/blob/082fe2b5a83571dec4aa97580af0fe8cf2a5214e/django/contrib/gis/gdal/envelope.py#L135
4. consider-using-max-builtin:
   Consider using 'MaxY = max(MaxY, maxy)' instead of unnecessary if block
   https://github.com/django/django/blob/082fe2b5a83571dec4aa97580af0fe8cf2a5214e/django/contrib/gis/gdal/envelope.py#L137

Effect on sentry:
The following messages are now emitted:

1. consider-using-max-builtin:
   Consider using 'max_pk = max(max_pk, item.pk)' instead of unnecessary if block
   https://github.com/getsentry/sentry/blob/3f2619d8e23717d55968e5a1f43b45831a393566/src/sentry/backup/services/import_export/impl.py#L529

The following messages are no longer emitted:

1. consider-using-max-builtin:
   Consider using 'max_pk = max(max_pk, pk)' instead of unnecessary if block
   https://github.com/getsentry/sentry/blob/3f2619d8e23717d55968e5a1f43b45831a393566/src/sentry/backup/services/import_export/impl.py#L529

This comment was generated for commit f9330c5

[Pierre-Sassoulas]

Great first contribution, the primer result is a pleasure to see 🎉