*: fix newtidb encoder

[xhebox]

Signed-off-by: xhe xw897002528@gmail.com

What problem does this PR solve?

Issue Number: ref #8, pingcap/log section

Problem Summary: I made some mistakes when porting the encoder of pingcap/log. This PR should hopefully fix these issues.

What is changed and how it works:

1. Correctly escape characters, but not all characters as pingcap/log. The requirements are: first, double quotes if needed; second, one message one line, no wrapping.
2. Also escape AppendReflected and AddString, it is missed in my previous PR.
3. AppendByteString will encode to hex automatically. This does not violate the RFC. It actually makes more sense. In tikv, []byte are mostly keys, which will be encoded into a human readable format. But that is not true in go or other components. Just convert all []byte to hex. If you need custom encoding, use zap.Stringer.
4. remove encodeError. This workaround is already fixed by *: new tls configuration for operator #80
5. fix problems with logger.With... etc, commented the reason for changes.

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
• No code

Notable changes

• Has configuration change
• Has HTTP API interfaces change (Don't forget to add the declarative for API)
• Has weirctl change
• Other user behavior changes

Release note

Please refer to Release Notes Language Style Guide to write a quality release note.

None