General check and fix cleanup

[lue-bird]

• [x] Supply all checkInfo arguments implicitly
• [x] group related type properties
• [x] remove fixToLeft/RightRange in favor of keepOnlyFix / replaceBySubExpressionFix
• [x] remove errorToLeft/RightRange in favor of operatorRange / Range.combine of fn and side
• [x] tweak operation error infos
  • [x] (-), (+), (*), (/), (//), (++), (<), (<=), (>), (>=), (&&), (||), (&&), (==), (/=)
  • [x] unnecessaryMessage, unnecessaryDetails, alwaysSameDetails and other error helpers
• [x] lean more into operationSides
• [x] Add unnecessaryCompositionAfterEmptyCheck
• [x] Add last.argCount to CompositionIntoCheckInfo
• [x] allow ConstructWithOneArg as empty directly by requiring an extra is property
• [x] listDetermineLength use getSpecificFnCall for singleton

Note that unnecessaryCompositionAfterEmptyCheck enables new simplifications, e.g. Task.map f << Task.fail --> Task.fail which are deliberately not included in this PR.

Switching to Fn.Array.map will be the next PR

[github-actions[bot]]

The branch can be tried out by running:

elm-review --template jfmengels/elm-review-simplify/preview

[jfmengels]

LGTM so far (note for me, last commit I checked was Remove unused errorToLeft/RightRange)

[lue-bird]

Fighting https://github.com/elm/compiler/issues/2312, this somehow worked out now. However, I'm not confident this extensible record type alias extending TypeProperties thing won't cause headaches in the future.

E.g. setChecks has exactly one property nesting (the most intuitive one) which leads to a compiler while any other nesting compiles fine.

Sensible solutions might be to not alias TypeProperties in every other properties type alias or to completely switch to record fields for the properties. What do you say?

[jfmengels]

I'm fine with not having TypeProperties in every other properties type alias :+1: But feel free to switch to the other approach if you think it will work better :+1:

[jfmengels]

Great work :blush: