Upgrade Django to 3.2 LTS, update various dependencies to ensure compatibility and solve deprecation warnings.

Closes #257 (closed) Part of #295 (closed)

Changelog

Features

• Django Upgrade to 3.2 LTS (b4a9cf9d): Upgraded the project to use Django 3.2 LTS, marking a significant update for long-term support and compatibility. 3.2 is supported with security updates until April 2024, and an upgrade to 4.2 LTS should be quite straightforward from here. The previous 3.1 release had reached EOL quite some time ago.
• New 'testd' Make Command for Un-silenced Pytest Output (2b6f5682): Introduced a new 'testd' command in the Makefile for executing pytest with detailed, un-silenced output. Useful for debugging.

Fixes

• API Response Rendering in TutorListTests (26447c97): Modified TutorListTests to ensure fresh API response rendering for each test method, addressing ContentNotRenderedError due to Django 3.2's testing behavior changes.
• TypeError in FeedbackCreateTestCase (870a2e22): Resolved a TypeError in FeedbackCreateTestCase by changing the lambda function for the 'url' method to a standard instance method, correcting issues post Django 3.2 LTS upgrade.

Refactor

• SemVer Usage Update (30a0ec8b): Updated the usage of semantic versioning (semver) to resolve deprecation warnings

Chores

• Dependencies Update for Django 3.2 Compatibility:
  • Updated django-silk for deprecation warnings and improved Django 3.2 support (ff052a8c).
  • Updated drf-cors-headers in anticipation of Django 3.2 upgrade (b8bfd3f6).
  • Updated Django REST Framework (DRF) and drf-yasg to fix deprecation warnings (d98d57f7).
  • Updated django-constance for Django 3.2 and future 4.2 support (b6c37805).
  • Updated pytest and related dependencies (016fda92).
  • Updated Jupyter-related dependencies and removed pyzmq due to conflicting dependencies and apparent non-usage in the project (46e98916).