*: fix log format

[xhebox]

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

What problem does this PR solve?

Issue Number: close None

Problem Summary: Since we switched to manual creation of zapcore.Core, we lost some default configuration that is present in zap.NewProductionLogger, causing the new encode behave differently with the old log format.

What is changed and how it works:

1. correct time format
2. all upper case level
3. add xxx.go:xxx, i.e. caller information

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 tiproxyctl change
• Other user behavior changes

Release note

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

None