This is an automated cherry-pick of #35625

What problem does this PR solve?

Issue Number: close #35624

Problem Summary:

Because tidb persists global variables to the cluster, setting configuration requires first waiting for TiDB to listen and then a mysql client to connect and set initial values of the variables. This requires some clumsy automation scripts. It's much easier if the server can accept a SQL file with which to specify a set of SQL commands to execute on first bootstrap only.

What is changed and how it works?

A new option -initialize-sql-file is added to the tidb-server binary.

Check List

Tests

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

Side effects

• Performance regression: Consumes more CPU
• Performance regression: Consumes more Memory
• Breaking backward compatibility

Documentation

• Affects user behaviors
• Contains syntax changes
• Contains variable changes
• Contains experimental features
• Changes MySQL compatibility

Release note

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

A new option `-initialize-sql-file` is added to the tidb-server binary. This can be used as part of automation to specify an initial set of SQL commands to run on the first bootstrap of the tidb cluster.