Make clang-format less strict

[F1F7Y]

Docs: https://clang.llvm.org/docs/ClangFormatStyleOptions.html

Makes clang-format less strict and also changes some things to make the code more readable ( this will very obviously require some parts to be changed manually ).

As I took my own spin on formatting and these changes are very individual based i expect this to take time, unlike other PRs.

[F1F7Y]

also thinking about setting

PointerAlignment: Right
ReferenceAlignment: Right

[pg9182]

Can we limit this PR to relaxing rules rather than drastically changing formatting?

[pg9182]

Looks good in general.

[pg9182]

LGTM. There's some other clang-format settings we should change too, but this is good.

[Jan200101]

Looks good but will probably cause conflicts in some PRs

[ASpoonPlaysGames]

Before this gets merged someone should merge main into it, and then fix the formatting

[Jan200101]

re-reviewing since changes were made since my last review.

Still looks good, some additional format changes could be made but its best to split any more changes into new PRs

[GeckoEidechse]

Quick skim and the changes are an improvement. That being said:

1. I found out today that clang-format does tab indentation incorrectly, check my rant here Define indent size in editorconfig #550 (comment)
   (spaces superiority)
2. When merging I will first merge only the config change and then the formatting changes in a separate commit so that I can then add that commit to the .git-blame-ignore-revs file so that git blame is still readable
3. I'll probably merge the other PRs that are ready to merge first so that we don't cause a bunch of PRs that are ready to merge to merge conflict.

[GeckoEidechse]

For merging this we would first only merge the .clang-format related changes and then in a second commit, made by Northstar <[email protected]> we would apply the formatting changes so that we then can add the formatting commit to .git-blame-ignore-revs so that it doesn't show up in git blame ^^

So basically just revert the actual formatting changes (they are causing merge conflicts rn anyway) so that only the config changes are left and then we can merge this ^^

[F1F7Y]

Superseded by #772