Tracking issue for unifying log library

[SabaPing]

This issues tracking the progress for "Unify Log Library for Golang Projects"

What problem does this PR solve?

The primary goal is to clean up the logging component. TiDB (and other golang projects) depends on two different third part log components, which are logrus and zap. This creates unnecessary complexity. In addition, there are some other logging flaws in code.

Task Check List

• Write a proposal, Proposal: Unify Log Library for Golang Projects #24181
• Refactor TiDB log library, *: clean up the logging component #23534
• Refactor PD log library
• Refactor BR log library
• Refactor TiUP log library
• deprecate InitZapLogger and prefer InitLogger #25380
• remove deprecated InitZapLogger #26314

Release note

• No release note.

[SabaPing]

Doc Tasks:

• Update the logging-related content in the user documentation to clarify the logging configuration and format of each component.

[tisonkun]

Hi @SabaPing , what is the next step you would like to go?

If you don't have time to create a PR, you can create subtask issue on BR / PD / TiUP and describe task you'd like to do. And hopefully we can take some of them.

[tisonkun]

@SabaPing BR is merged into TiDB, you can take a look whether we should change something in the plan.

[SabaPing]

#23534 caused an issue of unwanted GRPC logs.
And it fixed by pr: #25454.

[SabaPing]

#23534 caused an issue #25716 that some slow log file configs not working. This made unexpected disk usage.

Fixed by pr: #27625

[SabaPing]

There is a pr that enables runtime logger configuration: session: add session var to update global logger max days