Use pre-commit.ci for linting repository

[dstansby]

I set up https://pre-commit.ci/ to run pre-commit on the repository. The advantage of this over github actions is you can leave a comment that says "pre-commit.ci autofix" on the PR, and it will push a commit that fixes any issues that can be automatically fixed.

I left the GH actions job that lints the template after a package is generated, as I don't think there's a way to replace that.

[paddyroddy]

Personally, I'd vote for consistency 🤷

[samcunliffe]

I'm 🤷 here. Do we want to recommend pre-commit.ci over running a linting job by ourselves in Actions? If so we should add that to the docs because it's a different to what we're recommending currently.

There's also the question of (legitimately) private RSE projects which this cookie-cutter would then be less useful for.

[paddyroddy]

There's also the question of (legitimately) private RSE projects which this cookie-cutter would then be less useful for.

I would for one approach for public & private. Unfortunately, many ARC projects are still private.

[dstansby]

👍 I buy the consistency between free/private repositories. I'll disable pre-commit.ci on this repo.