Use sanitized message in logs

[lmolkova]

spin-off from #25247

This PR

• fixes unsanitized (with newline) messages in logs
• adds a tiny perf improvement for it to avoid using regex for new line replacement

---

Benchmark

Benchmark                           Mode  Cnt    Score    Error  Units
MyBenchmark.customReplaceNewLine    avgt    6  433.248 ▒ 12.022  ns/op
MyBenchmark.replaceAllNewLine       avgt    6  731.998 ▒ 13.366  ns/op

MyBenchmark.customReplaceNoNewLine  avgt    6   11.642 ▒  0.140  ns/op
MyBenchmark.replaceAllNoNewLine     avgt    6   54.876 ▒  2.575  ns/op

 @Benchmark
  public void replaceAllNoNewLine(Blackhole bh) {
      bh.consume(NEW_LINE_PATTERN.matcher(logNoNewLine).replaceAll(""));
  }

  @Benchmark
  public void replaceAllNewLine(Blackhole bh) {
      bh.consume(NEW_LINE_PATTERN.matcher(logWithNewLine).replaceAll(""));
  }

  @Benchmark
  public void customReplaceNewLine(Blackhole bh) {
      bh.consume(sanitizeLogMessageInput(logWithNewLine));
  }

  @Benchmark
  public void customReplaceNoNewLine(Blackhole bh) {
      bh.consume(sanitizeLogMessageInput(logNoNewLine));
  }

[kasobol-msft]

I wonder if the expected value should be "t\hello world". i.e. should we replace \n or \r or \r\n with white space?
If somebody is processing logs in some sophisticated way (i.e. attempts to do NLP) "helloworld" and "hello world" may make a difference.
(this might be out of scope of this PR).