style: adjust clang-format rules

[ReenigneArcher]

Description

Adjust clang-format rules, mostly to adjust break after return type behavior.

Screenshot

Issues Fixed or Closed

Type of Change

• Bug fix (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)
• Dependency update (updates to dependencies)
• Documentation update (changes to documentation)
• Repository update (changes to repository files, e.g. .github/...)

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have added or updated the in code docstring/documentation-blocks for new or existing methods/components

Branch Updates

LizardByte requires that branches be up-to-date before merging. This means that after any PR is merged, this branch
must be updated before it can be merged. You must also
Allow edits from maintainers.

• I want maintainers to keep my branch updated

[ReenigneArcher]

See https://github.com/LizardByte/Sunshine/actions/runs/8072315274/job/22053784930 for all changes that will be applied when this PR is ready to merge.

[Hazer]

I made a proposal of changes in:
#2623

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 12.06%. Comparing base (26566cc) to head (2c10eba).

Additional details and impacted files

@@            Coverage Diff            @@
##           master    #2186     +/-   ##
=========================================
  Coverage   12.06%   12.06%             
=========================================
  Files          91       91             
  Lines       16206    16206             
  Branches     7684     7684             
=========================================
  Hits         1955     1955             
- Misses      11778    13668   +1890     
+ Partials     2473      583   -1890     

Flag	Coverage Δ
Linux	11.91% <ø> (ø)
Windows	13.05% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

see 31 files with indirect coverage changes

[FrogTheFrog]

Could we get this curly bracket on a new line? It looks very ugly in my opinion. Moving it still looks ugly, but less so...

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud