Fix solving problems in 3 consecutive runs

[paul-dingemans]

Description

False positive message

Display log message Format was not able to resolve all violations which (theoretically) can be autocorrected in file ... in 3 consecutive runs of format only when after the third consecutive run still a violation exists that can be autocorrected.

Closes #2129

Function signature wrapping

x wrapping of function signature in case the opening brace of the function body block exceeds the maximum line length. Fix upsert of whitespace into composite nodes.

Closes #2130

Checklist

Before submitting the PR, please check following (checks which are not relevant may be ignored):

• Commit message are well written. In addition to a short title, the commit message also explain why a change is made.
• At least one commit message contains a reference Closes #<xxx> or Fixes #<xxx> (replace<xxx> with issue number)
• Tests are added
• KtLint format has been applied on source code itself and violations are fixed
• CHANGELOG.md is updated
• PR description added

Documentation is updated. See difference between snapshot and release documentation

• Snapshot documentation in case documentation is to be released together with a code change
• Release documentation in case documentation is related to a released version of ktlint and has to be published as soon as the change is merged to master
• In case of adding a new rule, it needs to be added to experimental rules documentation