Make clang-format behave more sensible about northstarlauncher

[KittenPopo]

I recommend adding:

SpaceAfterLogicalNot: false
SpaceBeforeAssignmentOperators: true
SpaceBeforeCpp11BracedList: true
SpaceBeforeCtorInitializerColon: true
SpaceBeforeInheritanceColon: true
SpaceBeforeParens: ControlStatements
SpaceBeforeRangeBasedForLoopColon: true
NamespaceIndentation: All
AlignTrailingComments: false
AllowAllConstructorInitializersOnNextLine: false
AllowAllParametersOfDeclarationOnNextLine: true
AllowShortFunctionsOnASingleLine: Empty
AlwaysBreakAfterDefinitionReturnType: None
AlwaysBreakAfterReturnType: None
AlwaysBreakTemplateDeclarations: No
BinPackArguments: false
BinPackParameters: false
ExperimentalAutoDetectBinPacking: false
IndentCaseLabels: false
ObjCBinPackProtocolList: Auto
SpaceAfterCStyleCast: false
SpaceInEmptyParentheses: false
Standard: Cpp11

This fixes basically all the wacky issues with clang-format, and specifies some more strict formatting rules (I based this on what is already used in the code).

[cpdt]

These lines from @KittenPopo's config should be enough to fix those pathological "to the moon" cases:

BinPackArguments: false
BinPackParameters: false
ExperimentalAutoDetectBinPacking: false

clang-format 14 also supports AlignAfterOpenBracket: BlockIndent, which turns this:

NSMem::BytePatch(
    ba + 0x18ED8D,
    {
        0xC3 // jmp => ret
    });

into this, which is maybe a bit cleaner:

NSMem::BytePatch(
    ba + 0x18ED8D,
    {
        0xC3 // jmp => ret
    }
);

[KittenPopo]

Sweet, we should upgrade to 14!

into this, which is maybe a bit cleaner:

NSMem::BytePatch(
    ba + 0x18ED8D,
    {
        0xC3 // jmp => ret
    }
);

Much cleaner! This is what I was trying to get clang-format to do lol

[GeckoEidechse]

^--- @abarichello might wanna check that out ;)

[GeckoEidechse]

clang-format 14 only released like 3 weeks ago, so the action we use doesn't support it yet :c

I opened an issue with them for now to see if/when support will be added.

[GeckoEidechse]

Before messing with clang-format we should probably make sure that it accepts current code. Hence #143 to format code to current version of clang-format.