[Snyk] Security upgrade django from 1.8.19 to 4.2.17

[willc-work]

Snyk has created this PR to fix 2 vulnerabilities in the pip dependencies of this project.

Snyk changed the following file(s):

• requirements/generated/requirements-dev.txt

⚠️ Warning

model-mommy 1.2.4 has requirement Django<1.9, but you have django 3.2.25.
virtualenv 20.26.6 has requirement distlib<1,>=0.3.7, but you have distlib 0.3.6.
virtualenv 20.26.6 has requirement filelock<4,>=3.12.2, but you have filelock 3.2.1.
virtualenv 20.26.6 has requirement importlib-metadata>=6.6; python_version < "3.8", but you have importlib-metadata 2.1.3.
virtualenv 20.26.6 has requirement platformdirs<5,>=3.9.1, but you have platformdirs 2.0.2.

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• Max score is 1000. Note that the real score may have changed since the PR was raised.
• This PR was automatically created by Snyk using the credentials of a real user.
• Some vulnerabilities couldn't be fully fixed and so Snyk will still find them when the project is tested again. This may be because the vulnerability existed within more than one direct dependency, but not all of the affected dependencies could be upgraded.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Command Injection
🦉 SQL Injection

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud