Add a test for missing generics in stubs

[UnknownPlatypus]

I have made things!

Followup to this discussion #2384 (comment)

This introduce a test ensuring every generic we define in stubs are generic at runtime too.

This also adds the missing ones (SetPasswordForm, discussed above, being one of them)

See initial failing run

FAILED tests/test_generic_consistency.py::test_find_classes_inheriting_from_generic - AssertionError: classproperty is not patched in `ext/django_stubs_ext/patch.py`
  ConnectionProxy is not patched in `ext/django_stubs_ext/patch.py`
  Options is not patched in `ext/django_stubs_ext/patch.py`
  BaseIterable is not patched in `ext/django_stubs_ext/patch.py`
  ReverseOneToOneDescriptor is not patched in `ext/django_stubs_ext/patch.py`
  ForwardManyToOneDescriptor is not patched in `ext/django_stubs_ext/patch.py`
  SetUnusablePasswordMixin is not patched in `ext/django_stubs_ext/patch.py`
  SetPasswordForm(SetPasswordMixin, Form, BaseForm, RenderableFormMixin, RenderableMixin) is not patched in `ext/django_stubs_ext/patch.py`
  AdminPasswordChangeForm(SetUnusablePasswordMixin, SetPasswordMixin, Form, BaseForm, RenderableFormMixin, RenderableMixin) is not patched in `ext/django_stubs_ext/patch.py`
  SetPasswordMixin is not patched in `ext/django_stubs_ext/patch.py`
  ModelFormOptions is not patched in `ext/django_stubs_ext/patch.py`

[UnknownPlatypus]

This is annoying, we cannot easily patch these 2 because we end up importing the User model and it crashes if django.setup() was not called beforehand.

The recommendation from the readme to add the monkeypatch in the setting file might not be enough for this.

I commented the logs here for the moment because I'm not sure what is the best way to handle this (and if I add it, I need to find a way to silence this logger in test or it fails some snapshot)

Any idea on how to handle this @sobolevn ? (or @adamchainz maybe if you have some time)

[UnknownPlatypus]

I've documented a workaround for these symbols that seem to work on my django codebases.

If you use these generics, you'll have to rerun the monkeypatch after django is initialized.
We could also maybe expose another monkeypatch func for these

[sobolevn]

How long does it take to run this test in CI? (sorry, not from a work computer right now)

[UnknownPlatypus]

How long does it take to run this test in CI? (sorry, not from a work computer right now)

Locally it was ~230ms, ci not sure, I can activate pytest timings to check once I'm back home from my concert X)

[UnknownPlatypus]

How long does it take to run this test in CI? (sorry, not from a work computer right now)

1-1.3s in ci !

python3.10 - 1.10s call     tests/test_generic_consistency.py::test_find_classes_inheriting_from_generic 
python3.11 - 1.03s call     tests/test_generic_consistency.py::test_find_classes_inheriting_from_generic
python3.12 - 1.39s call     tests/test_generic_consistency.py::test_find_classes_inheriting_from_generic
python3.13 - 1.16s call     tests/test_generic_consistency.py::test_find_classes_inheriting_from_generic

[sobolevn]

Looks like a great starting point! Thanks a lot! It found many classes that we forgot to monkey patch :)