This is an automated cherry-pick of #45170

What problem does this PR solve?

Issue Number: close #45176

Problem Summary:
This problem should be that the load full schema takes 1min37s, that is, the lease period is exceeded, and there is no new load schema operation in the future. This error(Information schema is out of date) is reported when an SQL statement comes in.
Because the transaction will check the validity of the schema, and the validity check, if found txnTS bigger than schemaValidator.latestSchemaExpire, will quote this wrong.

What is changed and how it works?

Do a new reload to update schemaValidator.latestSchemaExpire, after the first reload in domain.Init.

In the future, we need to optimize the load schema operation.

Check List

Tests

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

Case 1
Local cluster, 1 TiDB, 1 TiKV.
Make the first reload take 50s(do sleep in function) in domain.Init for master branch as test master.

Before this PR:
Upgrade from v6.5.2 to test master, failed to upgrade due to Information schema is out of date.
After this PR:
Upgrade from v6.5.2 to test master, successful to upgrade.

Case 2
Benchbot cluster, 1 TiDB, 3 TiKV.
Make the first reload take 54s(create 500,000 tables ) in domain.Init for master branch as test master.

Before this PR:
Upgrade from v6.5.2 to test master, failed to upgrade due to Information schema is out of date.
After this PR:
Upgrade from v6.5.2 to test master, successful to upgrade.

• 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.

None