[security] build(deps): bump django from 3.0.6 to 3.0.7

[dependabot-preview]

Bumps django from 3.0.6 to 3.0.7.

Commits

• 44da7ab [3.0.x] Bumped version for 3.0.7 release.
• 84b2da5 [3.0.x] Fixed CVE-2020-13254 -- Enforced cache key validation in memcached ba...
• 1f2dd37 [3.0.x] Fixed CVE-2020-13596 -- Fixed potential XSS in admin ForeignKeyRawIdW...
• 256d297 [3.0.x] Added release date for 2.2.13 and 3.0.7.
• 8734a02 [3.0.x] Updated link to Celery.
• d22f678 [3.0.x] Refs #31485 -- Backported jQuery upgrade to 3.5.1.
• b9db041 [3.0.x] Adjusted URL example in tutorial.
• caf7c46 [3.0.x] Fixed #31643 -- Changed virtualenv doc references to Python 3 venv.
• 9297a3e [3.0.x] Fixed typo in docs/ref/templates/language.txt.
• 2638627 [3.0.x] Fixed #31570 -- Corrected translation loading for apps providing terr...
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Pull request limits (per update run and/or open at any time)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)

[codecov]

Codecov Report

Merging #28 into project-set-up will not change coverage.
The diff coverage is n/a.

@@               Coverage Diff               @@
##           project-set-up      #28   +/-   ##
===============================================
  Coverage           80.23%   80.23%           
===============================================
  Files                   7        7           
  Lines                 258      258           
===============================================
  Hits                  207      207           
  Misses                 51       51           

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 733baf5...4bb11fb. Read the comment docs.

[dependabot-preview]

We've just been alerted that this update fixes a security vulnerability:

Sourced from The GitHub Security Advisory Database.

Data leakage via cache key collision in Django
An issue was discovered in Django 2.2 before 2.2.13 and 3.0 before 3.0.7. In cases where a memcached backend does not perform key validation, passing malformed cache keys could result in a key collision, and potential data leakage.

Affected versions: [">= 3.0.0, < 3.0.7"]

[dependabot-preview]

Superseded by #42.