Docstring improvements

[xaviernogueira]

Closes #186
@abkfenris I will be a free-agent in a week or two, and plan to contribute in this ecosystem more heavily. I figured documenting and type-hinting the codebase would be an opportunity to refresh on the inner-workings.

Changes:

• I added Ruff's pydocstyle to our pyproject.toml. This includes docstring formatting as part of the pre-commit. I have it set to ignore the tests/ and docs/ directories as that seems fussy, but I am happy to cover those two as well.
• I also have it set to ignore three docstring rules, D100 (requires docstrings for all modules / .py files), D107 (requires docstrings for all init.py), and D104 (simular to D107, requires all packages to have a docstring). Happy to change this. I find module docstrings a bit overkill, especially as the name of the module should be semantically relevant, and all classes / functions have docstrings.
• I converted all docstrings to Google napolean style.
• I added typehints where missing, I also used pyright to make check that all typehints are correct, and fixed some bad ones.
• Very minor syntax changes to satisfy pyright best practices. No changes to logic.
• I added pre-commit to the dev environment requirements.txt.

[xaviernogueira]

Everything seems ready to go (all tests passing), except CodeCov.

[xaviernogueira]

Unrelated to docstring update: Since I am a bit of a perfectionist having the CodeCov failure bothered me. To address it, I looked at the coverage report and saw that the logic to catch uninitialized plugins (throws an AttributeError) was un-tested.

I decided to write a test to capture this, but in doing so, realized that the exception-handling logic was flawed!

If one passes in an uninitialized plugin, instead of making it to the try/except block, an AttributeError will be thrown as the .name attribute cannot be read (that is unless an optional plugin_name is provided to register_plugin).

I expanded the try/except block to contain both the plugin.name reading, as well as the previously captured block. I added a test for this as well.

All checks passing now 😄 @abkfenris

[abkfenris]

Thanks for chasing down all the types and cleaning up the documentation! There are a few small things, one being a place where we likely had the typing wrong before.