Preserve breaking conditional statement

[matthewnessworthy]

📌 What Does This PR Do?

Adds a new preserve_breaking_condition_statement formatter setting that preserves multi-line
condition layouts in control structures (if, elseif, while, do-while, switch, match)
following PER Coding Style 3.0 rules.

🔍 Context & Motivation

The formatter already has preserve_breaking_conditional_expression for ternary expressions, but
there's no equivalent for control structure conditions. When a developer intentionally breaks a
complex condition across multiple lines for readability, the formatter should respect that layout
when this setting is enabled — placing each boolean operator on its own line and the closing
parenthesis on its own line.

php-fig.org/per/coding-style#51-if-elseif-else

Expressions in parentheses MAY be split across multiple lines, where each subsequent line is indented at least once. When doing so, the first condition MUST be on the next line. The closing parenthesis and opening brace MUST be placed together on their own line with one space between them. Boolean operators between conditions MUST always be at the beginning.

🛠️ Summary of Changes

• Feature: Added preserve_breaking_condition_statement bool field to FormatSettings and
  RawFormatSettings via the generate_formatter_settings! macro, defaulting to false.
• Feature: Set preset values — Pint, Tempest, Drupal = true; Default, PSR-12, Hack = false.
• Feature: Implemented must_break detection in print_condition() using
  has_new_line_in_range between the opening parenthesis and the condition.
• Feature: Added must_break_condition flag to FormatterState, threaded through to
  binaryish.rs to force hard line breaks before binary operators when inside a must-break condition.

📂 Affected Areas

• Linter
• Formatter
• CLI
• Dependencies
• Documentation
• Other (please specify):

🔗 Related Issues or PRs

Related to #869

📝 Notes for Reviewers

When enabled, a multi-line condition like:

if (
    $foo && $bar
) {
becomes:
if (
    $foo
    && $bar
) {

Single-line conditions are never forced to break. When disabled (the default), existing behavior is
unchanged — all 366 existing tests pass with zero regressions.

[azjezz]

LGTM. But before we can merge, please remove Claude from git history.

I don't mind using Claude, but it should never be in commit history for git blame :)

[matthewnessworthy]

@azjezz sure thing, I'll make the changes soon.
Thanks for the review and being accepting of the change

[azjezz]

@matthewnessworthy you should use just fix, it will fix formatting and clippy issue

[matthewnessworthy]

@azjezz i ran just fix, but it changed a couple of extra files, please let me know if that's fine, or if i should revert that commit in favour of running cargo fix

[matthewnessworthy]

@azjezz rebased, formatted, and conflicts fixed