Add pre-commit and use ruff

[JasonGrace2282]

Proposed changes

• Use pre-commit for linting/formatting
• Ideally maintainers will add pre-commit ci so that if the pre-commit fails, fixes will be pushed without having to run scripts.
  • Otherwise when creating a virtual environment, you can run pre-commit install and it should run pre-commit locally whenever you commit
• Change from black+autopep8 to ruff
  • Faster:
  • Drop in replacement for black: https://docs.astral.sh/ruff/formatter/#black-compatibility
  • Flake8 plugins included
  • Configurable in pyproject.toml

Brief description of rationale

Running scripts is annoying lol

Summary of Changes

• Add .pre-commit-config.yaml
  • Also adds some config for pre-commit ci if it is decided to be added
• Add pre-commit and ruff to dependencies
• Changes test pipeline to run pre-commit run --all-files instead of scripts for formatting/linting
• Deprecate the format scripts

Note

PR #1673 should be merged before this to see if all checks pass.
I just tested locally, there are about ~11 files that are changed after merging it. Once it's merged I'll push a commit updating this PR with those 11 files.

A similar change has been merged into tin, see tjcsl/tin#21

Progress

• scripts/format.sh
• scripts/lint.sh
• scripts/build_sources.sh
  • See Remove Ion.egg-info and build_sources.sh #1669 ?
• scripts/static_templates_format.sh

[JasonGrace2282]

To reiterate what I said on matterless:
The current problem is (to the best of my knowledge) that black and autopep8 interfere with each other. Black will format some files, then autopep8 will go in and fix those. This was fine in scripts where it simply merged both outputs (with autopep8 taking priority), but with pre-commit it counts a check as a fail if it modifies files. As such, both black and autopep8 will fail each run (black being unhappy with autopep8 and vice versa).
The possible solutions to this I can think of include:

• Remove autopep8 and stick with black
• Remove black and only use autopep8
• Don't use either, and use one formatter (something like ruff)
  • This is my preferred option due to ruff's speed, similarity to black, and a built in linter (removing the need for flake8).
• Do something like:

- repo: local
  hooks:
    id: format
    entry: ./scripts/format.sh && test -z "$(git status --porcelain=v1)"

(which I'm not sure would work with pre-commit ci)

@alanzhu0 @NotFish232 would be nice to get a second opinion on this, when you find the time of course ;)

[JasonGrace2282]

I think this PR is mostly ready to be reviewed, just need to find out what's causing the chaos with sorting imports and spacing with slicing.
Some benchmarks on my system:

• time pre-commit run --all-files takes 11.32 seconds (user)
• time ruff check intranet/**/*.py takes 0.45 seconds (user)
• time ruff lint intranet/**/*.py takes 0.04 seconds (user)

Since the diff is very large, I moved it into a separate PR: #1673

[JasonGrace2282]

In order to get the tests to pass (specifically flake8) in #1673, I had to make some changes that don't agree with the ruff (or black for that matter!). As such, the changes in that PR aren't 100% reflective of the changes needed here (but it's a pretty small and easy to review diff after that PR is merged).

On another note, if you're wondering why there is a formatting CI run that never completes, it's because it's marked as required in the repository settings.