[Inf1mum]

Closes #834

Summary

• show a hint when a failing toContain / toContain.ignoringCase search criterion would have matched if \r\n had been used instead of \n in the expected string (wording as agreed in warn if a CharSequence.contains and the like did not match because of different line endings #834)
• the hint is shown per search criterion and only if the expectation would have been met with the fixed line separators; it is not shown for notToContain (such an expectation cannot fail because a search criterion did not match) nor for regex criteria
• add DescriptionCharSequenceExpectation.WARNING_DIFFERENT_LINE_SEPARATORS translation (en_GB) and update the api dumps
• add shared spec AbstractCharSequenceToContainLineSeparatorsHintTest with Fluent and Infix implementations

Testing

• :atrium-specs:compileKotlinJvm
• :atrium-api-fluent:jvmTest --tests "ch.tutteli.atrium.api.fluent.en_GB.CharSequenceToContainLineSeparatorsHintTest" and all other CharSequence* tests (435 passing)
• :atrium-api-infix:jvmTest --tests "ch.tutteli.atrium.api.infix.en_GB.CharSequenceToContainLineSeparatorsHintTest" and all other CharSequence* tests (435 passing)
• :atrium-translations-en_GB:apiCheck, :atrium-logic:apiCheck

---

I confirm that I have read the Contributor Agreements v1.0, agree to be bound on them and confirm that my contribution is compliant.