Add the E and F Ruff rules

[ddabble]

This depends on #792.

Proposed changes

• E - flake8/pycodestyle (Error)
• F - flake8/Pyflakes

Also upgraded ruff-pre-commit to v0.15.0.

Review guidance

Checklist

(If any of the points are not relevant, mark them as checked, so that it's easy to see which points you've handled or not)

• I've run makemigrations, makemessages and compilemessages
• I've written tests that fail without these changes (if relevant/possible)
• I've manually tested the website UI with different device layouts
  • Most common is to test with typical screen sizes for mobile (320-425 px), tablet (768 px) and desktop (1024+ px), which can easily be done with your browser's dev tools
• I've manually tested with different users locally
  • This can be e.g. anonymous users (i.e. not being logged in), "normal" non-member users, members of different committees, and superusers
• I've made sure that my code conforms to the code style guides
  • It's not intended that you read through this whole document, but that you get yourself an overview over its contents, and that you use it as a reference guide / checklist while taking a second look at your code before opening a pull request
• I've attempted to minimize the number of common code smells
  • See the comment for the previous checkbox
• I've added documentation
  • E.g. comments, docstrings, or in the README
• I've added my changes to the "Unreleased" section of the changelog, together with a link to this PR
  • Mainly the changes that are of particular interest to users and/or developers, if any
• I've added a "Deployment notes" section above and labelled the PR with has-deployment-notes
  • ...if anything out of the ordinary should be done when deploying these changes to the server (e.g. adding/removing an environment variable, manually creating/changing some objects, running a management command, etc.)
• I've structured my commits reasonably
  • Some tips on this can be found in "Write Better Commits, Build Better Projects" and in the code style guides
  • Restructuring commits after they've already been committed, can be done using e.g. interactive rebase; see the Git docs on rewriting history

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 88.01%. Comparing base (b84426d) to head (e08480c).

Additional details and impacted files

@@                    Coverage Diff                    @@
##           add-max-line-length-rule     #793   +/-   ##
=========================================================
  Coverage                     88.01%   88.01%           
=========================================================
  Files                           153      153           
  Lines                          6225     6225           
=========================================================
  Hits                           5479     5479           
  Misses                          746      746           

Files with missing lines	Coverage Δ
src/make_queue/forms/machine.py	97.46% <ø> (ø)
src/users/models.py	94.28% <100.00%> (ø)
src/web/management/commands/runserver.py	0.00% <ø> (ø)

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.