style: break lines more often, allow multiline params

[Hazer]

Description

I propose those changes, so for example:

  constexpr auto MAX_GAMEPADS = std::min(static_cast<std::size_t>(platf::MAX_GAMEPADS), sizeof(std::int16_t) * 8);

breaks instead like this:

  constexpr auto MAX_GAMEPADS = std::min(
    static_cast<std::size_t>(platf::MAX_GAMEPADS), 
    sizeof(std::int16_t) * 8
  );

Also, ensures most places don't do:

BOOST_LOG(debug)  << "--begin controller touch packet--"sv << std::endl
                  << "controllerNumber ["sv;

And do

BOOST_LOG(debug) 
  << "--begin controller touch packet--"sv << std::endl
  << "controllerNumber ["sv;

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

[Hazer]

Explanation

• BreakBeforeBinaryOperators: NonAssignment: Ensures that binary operators (like <<) are treated appropriately for breaking lines.
• PenaltyBreakBeforeFirstCallParameter: 1: Encourages breaking before the first call parameter, making the first line shorter.
• PenaltyBreakComment: 1, PenaltyBreakString: 1: Lowers the penalty for breaking at these points, encouraging breaks.
• PenaltyBreakFirstLessLess: 0 Minimizes the penalty for breaking before the << operator, making it more likely that clang-format will break lines at these points.
• PenaltyExcessCharacter: 1000000: Adds a high penalty for exceeding the maximum line length, ensuring lines are broken earlier.