Add pre commit and migrate to ruff

[Saransh-cpp]

• add pre-commit
• use ruff
• remove flake8
• update docs
• add .git-blame-ignore-revs to preserve git blame messed up by the pre-commit commit

This should be safe to merge before the branches are merged.

Additionally, pre-commit.ci should be activated for liionpack (it isn't activated right now).

[Saransh-cpp]

Weirdly, the workflows fail on PyBaMM develop too.

[TomTranter]

Hey @Saransh-cpp thanks for this. I've just merged another PR into develop which should fix these failing tests

[codecov]

Codecov Report

Merging #232 (7cd7902) into develop (4e4c16e) will decrease coverage by 0.01%.
The diff coverage is 100.00%.

Additional details and impacted files

@@             Coverage Diff             @@
##           develop     #232      +/-   ##
===========================================
- Coverage    94.78%   94.77%   -0.01%     
===========================================
  Files           11       11              
  Lines         1188     1187       -1     
===========================================
- Hits          1126     1125       -1     
  Misses          62       62              

[Saransh-cpp]

@TomTranter can you enable https://pre-commit.ci for liionpack? pre-commit.ci will make formatting a breeze for PRs.

[TomTranter]

@TomTranter can you enable https://pre-commit.ci for liionpack? pre-commit.ci will make formatting a breeze for PRs.

What should I do? The docs say "nothing is needed beyond the .pre-commit-config.yaml file you already have!"