Update scalafmt

[mdedetrich]

This PR does the following things

• Updates scalfamt to the latest version as well as applying project.git = true. Not only is this faster since it only applies scalafmt on diffed files (as determined by git) but its neccessary so that scalafmt doesn't format git submodules
  • Also adds specific source files which are sensitive to formatting explicitly to the excludePaths list. There are other solutions for this (such as using format:off/format:on in the source file) but this to me appears the least brittle when it comes to testing.
• Applies scalafmt and places this in its own separate commit so that it can optionally be ignored with .git-blame-ignore-revs in a future PR
• Adds a github workflow action that checks if the entire codebase is committed. This can be added as a branch check to essentially prevent merging of PR's that are not formatted. I personally find this the best quality of life way to enforce code formatting (as opposed to solutions such as formatting on commit)

[mdedetrich]

@rolandtritsch The PR is ready, when merging it either do Merge commit or Rebase and merge but NOT squash and merge since I need the Apply scalafmt commit to remain in tact as I will add that to .git-blame-ignore-revs in a future PR.

Also you can add the Scalafmt / Code is formatted to the github repo branch status check after this PR is merged.

[rolandtritsch]

Hi @mdedetrich. Looks good. Rebased/merged it.