Add the I and TID252 Ruff rules

[ddabble]

This depends on #793.

Proposed changes

• I - isort
• TID252 - relative-imports
  • Makes it less of a hassle to remember when to do relative and when to do absolute imports, and makes it somewhat easier to read the code through e.g. GitHub

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

❌ Patch coverage is 98.68421% with 2 lines in your changes missing coverage. Please review.
✅ Project coverage is 88.01%. Comparing base (c3048c4) to head (bca0932).
⚠️ Report is 2 commits behind head on main.

Files with missing lines	Patch %	Lines
src/checkin/api/views.py	0.00%	1 Missing ⚠️
src/web/management/commands/compilemessages.py	0.00%	1 Missing ⚠️

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #794   +/-   ##
=======================================
  Coverage   88.01%   88.01%           
=======================================
  Files         153      153           
  Lines        6225     6225           
=======================================
  Hits         5479     5479           
  Misses        746      746           

Files with missing lines	Coverage Δ
src/announcements/admin.py	100.00% <100.00%> (ø)
src/announcements/forms.py	100.00% <100.00%> (ø)
...rc/announcements/templatetags/announcement_tags.py	100.00% <100.00%> (ø)
src/announcements/urls.py	100.00% <100.00%> (ø)
src/announcements/views.py	100.00% <100.00%> (ø)
src/card/formfields.py	93.33% <100.00%> (ø)
src/card/modelfields.py	100.00% <100.00%> (ø)
src/card/utils.py	46.15% <100.00%> (ø)
src/card/validators.py	100.00% <ø> (ø)
src/card/views.py	56.00% <100.00%> (ø)
... and 90 more

🚀 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.

[ddabble]

We've agreed to accept these PRs that mainly just adds linter rules, so merging without approval :)