fields.E305 is raised on ManyToManyFields with related_name='+' in models in different apps but with the same name.

[Aleksey Ruban]

Django raises an error during creation a db migration if two models with the same name refer to the same model in m2m field. related_name='+' or 'foo+' don't impact anything.
In some my project there are 50 apps and almost each one has a model with the same name. So I have to come up with a related name and write it in for each m2m field.
Just try to make a migration for my test project
​https://github.com/rafick1983/django_related_name_bug

[Mariusz Felisiak]

Thanks for the report. It looks that app_label is missing in ​ManyToManyField.contribute_to_class():

self.remote_field.related_name = "_%s_%s_%s_+" % (cls._meta.app_label, cls.__name__.lower(), name)

[Mariusz Felisiak]

​PR

[Mariusz Felisiak <felisiak.mariusz@…>]

In a9a7421a:

Fixed #32294 -- Prevented ManyToManyField's hidden related name collisions between apps.