Adding mypy as an option to run

[eirikurj]

Purpose

Per title.

Closes #17.

Expected time until merged

Type of change

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (non-backwards-compatible fix or feature)
• Code style update (formatting, renaming)
• Refactoring (no functional changes, no API changes)
• Documentation update
• Maintenance update
• Other (please describe)

Testing

Checklist

• I have run ruff check and ruff format to make sure the Python code adheres to PEP-8 and is consistently formatted
• I have formatted the Fortran code with fprettify or C/C++ code with clang-format as applicable
• I have run unit and regression tests which pass locally with my changes
• I have added new tests that prove my fix is effective or that my feature works
• I have added necessary documentation

[sseraj]

Looks pretty good, just one comment

[DavidAnderegg]

Thank you. I think we need to have a slightly different way to run mypy

[lamkina]

Can we move the base ref branch to dev? This should be a PR to dev first, then we can move it to main and tag.

[DavidAnderegg]

its ok for me.

[eirikurj]

@lamkina sure I can do that. The reason why this PR is to main is that it was made before settled on the feature->dev->main. Will close this one and make a new one.