Format code to pass new format checks

[NielsJPeschel]

Proposed changes

Adds Pretty as dev dependency as well as a format check to ensure code adheres to a standard

Types of changes

What types of changes does your code introduce?
Put an x in the boxes that apply

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

• I have read the CONTRIBUTING doc
• I have added tests that prove my fix is effective or that my feature works
• I have added necessary documentation (if appropriate)
• Any dependent changes have been merged and published in downstream modules

[nthurow]

Are you sure we need this file? When we run prettier we are pointing to .gitignore, right?

[NielsJPeschel]

Good point! Done

[nthurow]

This feels so much better 😄

[NielsJPeschel]

This feels so much better 😄

Right?? Lint is up next