Continuously bump django-stubs and djangorestframework-stubs

Updated issue

( Updated Dec 2024 by @kdmccormick )

To maximize the stability and usefulness of our typechecking, we should always be constraining django-stubs to a version which is compatible with whatever our django and mypy version is. Generally, for django-stubs, that will be the latest patch release of the same major version as django or one major version greater.

Also djangorestframework-stubs may or may not need to be constrained.

There unfortunately isn't an easy way to bump those constraints automatically, so we'll leave this GitHub issue open indefinitely.

Original issue

( Created Aug 2024 by @huniafatima-arbi )

The version of django-stubs we can use depends on which Django release we're using 1.16.0 works with Django 3.2 through 4.1. Once django is updated we can remove this constraint

The issue does not name a file or test. Start by locating the project’s Django and mypy dependency constraints, then read the linked django-stubs compatibility guidance. Update the constraints to match the supported Django version and verify the dependency set remains compatible.