Update the docs links to the latest versions of Django.

Author: tim-schilling

docs/lab1.md

@@ -118,7 +118,7 @@ Let's consider what we know:
 
 - Does the file show up on the server side?
   - Using the IDE's debugger, a ``breakpoint()`` line or a print statement, inspect
-    [``request.FILES``](https://docs.djangoproject.com/en/4.1/ref/request-response/#django.http.HttpRequest.FILES).
+    [``request.FILES``](https://docs.djangoproject.com/en/stable/ref/request-response/#django.http.HttpRequest.FILES).
   - Are there any files included? Is ``"open_graph_image"`` a key?
 - Is the file being sent from the browser to the server?
   - We can use the browser's Developer Tool's Network panel to inspect the request.

docs/lab2.md

@@ -62,14 +62,14 @@ is a never ending, relentless battle.
 
 #### Post listing admin
 The admin page suffers from a [N+1 problem](https://ddg.gg?q=N%2B1+django) and
-needs to make use of [``prefetch_related``](https://docs.djangoproject.com/en/4.1/ref/models/querysets/#django.db.models.query.QuerySet.prefetch_related)
+needs to make use of [``prefetch_related``](https://docs.djangoproject.com/en/stable/ref/models/querysets/#django.db.models.query.QuerySet.prefetch_related)
 since it renders each category of the post on the page. This can be chained on
 the QuerySet by overriding ``ModelAdmin.get_queryset``. The need for
 ``prefetch_related`` is evident from the 100 duplicated queries that are fetching data from the table
 ``newsletter_post_categories``. That table is the intermediate table used with
 a ``models.ManyToManyField``. There is a slight wrinkle in that the categories
 are being rendered in order of the categories' titles. In order to push that
-to the database, you must use a [``Prefetch``](https://docs.djangoproject.com/en/4.1/ref/models/querysets/#django.db.models.Prefetch)
+to the database, you must use a [``Prefetch``](https://docs.djangoproject.com/en/stable/ref/models/querysets/#django.db.models.Prefetch)
  object that specifies:
 
 ```python
@@ -164,7 +164,7 @@ squeeze all the speedy goodness out of the application.
 
 That said, consider the application(s) you work on. What are the most
 frequently used parts? What do you have in place to catch slowness?
-Could you benefit from using [``assertNumQueries(...)``](https://docs.djangoproject.com/en/4.1/topics/testing/tools/#django.test.TransactionTestCase.assertNumQueries)?
+Could you benefit from using [``assertNumQueries(...)``](https://docs.djangoproject.com/en/stable/topics/testing/tools/#django.test.TransactionTestCase.assertNumQueries)?
 
 
 ## Lab 2.2
@@ -302,12 +302,12 @@ Let's consider what we know:
     count.
   - This can be fixed by using an appropriate ``GROUP BY`` clause in the SQL.
   - What does the Django ORM's ``Count`` expression offer in terms of parameters?
-    - You can use the [docs](https://docs.djangoproject.com/en/4.1/ref/models/querysets/#id9)
-      or inspect [the code](https://github.com/django/django/blob/stable/4.1.x/django/db/models/aggregates.py#L145-L149)
+    - You can use the [docs](https://docs.djangoproject.com/en/stable/ref/models/querysets/#id9)
+      or inspect [the code](https://github.com/django/django/blob/stable/5.2.x/django/db/models/aggregates.py#L159-L163)
       (right click on ``Count`` and choose "Go To Definition") in
       your IDE if you're using PyCharm or VSCode.
     - We can see that ``Count`` subclasses [``Aggregate`` which has ``distinct`` as
-      a param](https://github.com/django/django/blob/e151df24ae2b0a388fc334a6f1dcb31110d5819a/django/db/models/aggregates.py#L25-L35).
+      a param](https://github.com/django/django/blob/stable/5.2.x/django/db/models/aggregates.py#L26-L33).
 
 ### Conclusion