Moving from pylint to ruff linter

[john-science]

Description

This PR moves the ARMI project from using the pylint linter to using the ruff linter.

That means that this PR is big, because we used to have # pylint: disable=xyz lines in like every Python file. But that's not necessary with ruff. Not only is ruff like 100x faster, it is easier to configure (see the top-level ruff.toml file I added).

Also, this PR fixes all ruff errors in the repo. This allows me to add a new GitHub Action just to run ruff on the code, like we do when we run black. This way we can prevent people from adding poorly formatted code to the repo.

Also, ruff has the MIT license, which is a big improvement over pylint.

---

Checklist

• This PR has only one purpose or idea.
• Tests have been added/updated to verify that the new/changed code works.

• The code style follows good practices.
• The commit message(s) follow good practices.

• The release notes (location doc/release/0.X.rst) are up-to-date with any important changes.
• The documentation is still up-to-date in the doc folder.
• The dependencies are still up-to-date in setup.py.

[opotowsky]

Every time you merge main in I feel a little guilt I haven't gotten to it yet. I know it's low priority, but I still expected to be done by now. I promise it's still on my radar, and should work nicely with my schedule in the coming couple of days

[opotowsky]

Ok I've started clicking view on files. Finally in progress!

[opotowsky]

Ok this PR looks good! I've also testing things internally and nothing has changed.

Nice work yet again, @john-science