Define a coding style and document it

> [!NOTE]
> Migrated from [augurlabs/augur#3697](https://github.com/augurlabs/augur/issues/3697)
> Originally opened by `@MoralCode` on 2026-02-15

---

We should document our style guide beyond just pylint configs (#197). This would include things like:

How logging should be done (#114 )
How errors should be raised (originally mentioned in https://github.com/chaoss/augur/pull/3695)
how/where to use helper functions and import them
Writing functions such that they are single-purpose (therefore unit testable) and dont require the kitchen sink to be imported at runtime in order to run