Spellchecking with codespell

[Zeitsperre]

Pull Request Checklist:

• This PR addresses an already opened issue (for bug fixes / features)
  • This PR fixes #xyz
• Tests for the changes have been added (for bug fixes / features)
  • (If applicable) Documentation has been added / updated (for bug fixes / features)
• CHANGES.rst has been updated (with summary of main changes)
  • Link to issue (:issue:number) and pull request (:pull:number) has been added

What kind of change does this PR introduce?

• Adds codespell for checking word spellings
• Configures codespell to ignore several French words and all current translations configurations.
• Adds a pre-commit hook for performing these checks on commit

Does this PR introduce a breaking change?

Yes, codespell is now a development dependency.

Other information:

https://github.com/codespell-project/codespell

[review-notebook-app]

Check out this pull request on 

See visual diffs & provide feedback on Jupyter Notebooks.

---

Powered by ReviewNB

[coxipi]

Just to know: Is the dev installation automatically used when git cloning xclim and doing mamba install -n my_env -f environment.yml? I think xscen has environment_dev.yml, but not xclim, so how does this work here?

[Zeitsperre]

That's how we've organized xclim here. When someone installs xclim into a conda environment with the dev recipe, it pulls the development libraries from PyPI. This hasn't been an issue to date, but if we wanted to mirror the xscen approach, adding this file into the codebase is feasible.

Perhaps worth discussing in a separate issue?

[coxipi]

I don't see a problem with this organization, I just wanted to understand it, to be sure I'm not using a wrong version by error.

[coxipi]

Nice to have. Seems to be working well, approved!

Note: There were some changes like x -> x. codespell does not make suggestions like this correct, just some unrelated completely manual changes while we're at it correct?