Fix CommaRule mismatch between violations and corrections

[norio-nomura]

• Add failing correction example from Autocorrect reports success even though nothing happens #466 to CommaRule
  Autocorrect reports success even though nothing happens #466 (comment)
• Rewrite CommaRule.correctFile(_:)
  Now corrections happen only on violations.
  Because assertCorrection(_:expected:) expects one correction for each corrections,
  and the rule added by 93e8e12 causes two corrections on previous logic.
  Fix Autocorrect reports success even though nothing happens #466
• Simplify the regular expression in CommaRule.validateFile(_:)
• Remove surplus map calls in rangesAndTokensMatching(_:)

[norio-nomura]

It seems more than two spaces after comma does not generate violation:

let a = [1,       2]

But correction happens for that.
I think correction's behavior may be correct.

[jpsim]

Fix CommaRule mismatch between violations and corrections.

[norio-nomura]

Thanks 🙏

[norio-nomura]

@jpsim I got a question while I'm implementing following won't generate violation and correction.
A:

func f(
  a: Int,
  b: Int // comma+newline+spaces
) {
}

Should we generate violation and correction for following?
B:

func f(a: Int
     , b: Int // newline+spaces+comma+space
) {
}

In other word, should we exclude line ending character on checking?
B is weird for me. But I can't determine whether it should do or not.

[norio-nomura]

Updated.

Should we generate violation and correction for following?
B:

I leave it generates on case B.

By applying this PR, The duration CommaRule of linting Carthage 0.14 increased from 154ms to 457ms.

[jpsim]

Travis is backlogged at the moment, but the only commit not tested is the changelog one, so this is good to merge.

These changes all look good to me. Thanks @norio-nomura!

[norio-nomura]

Thanks! 🙏