Improve code quality and checking

[asogaard]

• Adds automatic formating and checking of docstrings
• Adds automatic checking of static typing
• Updates all files to be compliant with these
• Changes call to _make_df to _convert_to_dataframe in ParquetToSQLiteConverter, as the former was renamed but the corresponding call was not update to reflect this.
• Adds new set of Code quality GitHub actions for checking each of the pre-commit hooks, replacing black which was the only thing we checked for before.
• Renames and regroups GitHub Actions to, e.g. ,Build, for clarity.
• Renames example script to a similar, imperative form.
• Added configupdater as setup dependency, as it is used in graphnet.pisa.

After this PR the recommended way to document functions is like:

def my_function(arg: int, other: str = "a") -> None:
    """Do something.

    A more detailed explanation of the logic behind `my_function` goes here.

    Args:
        arg: This thing.
        other: This other thing.
    """

That is, types and default values are document in the code itself. Any explanation of the logic is done in the docstring. For trivial function, the Args and Returns section on the docstring can be omitted. This should reduce duplication of e.g. type information, and the typing hinting allows for static type checking using mypy.

Closes #109
Closes #225
Closes #227
Closes #229

[RasmusOrsoe]

I'm not sure an IceCuber will recognize what is meant with "reconstructed features" here. I think "Class for extracting unfolded waveform pulses and associated OM information, such as position, orientation, etc." is more descriptive.

I don't think you necessarily have to change all the doc strings accordingly in this PR. Perhaps it's best if we discuss language first and iterate on doc string wording in a separate PR in the future.

[asogaard]

I think this is a good point, and this PR might be a good time to review our language as it will update all docstrings in the codebase. I'll try to keep this in mind going forward!

[RasmusOrsoe]

@asogaard really nice! I've added a single comment on the feature extractors; but as I mention, I think we can save that for later, if you prefer.

On another note; how does the automatic checks on doc strings and type hints affect our future PR's? Will the checks update the doc strings and type hints like black formatting does? Or will we have to consult output logs?

[asogaard]

... It's done... 😮‍💨

[RasmusOrsoe]

Well done!!

[asogaard]

As with all PRs of this size, there is a small change of a bug sneaking in, but as the vast majority of changes are purely to the "frosting", I figure it is still okay to merge.

Please see the original, updated comments for notes on the major changes. Please also see the slightly updated contributing guidelines. Finally, people who have been holding off on using pre-commit hooks ought to set it up now. I will also talk about this at next week's meeting.