ddl: fix warnings message when alter table nocache and cache again

[tiancaiamao]

What problem does this PR solve?

Issue Number: close #32692

Problem Summary:

What is changed and how it works?

'insert ignore into' will get a warning when the key exists, so use 'replace into' instead.

alter table cache -> alter table no cache -> alter table cache
The row already exists in the mysql.table_cache_meta, so 'insert ignore into' will get the warnings.

Alternative solution: let alter table no cache delete the record from the mysql.table_cache_meta...
But this is not safe when there are more than one client do it concurrently.

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

None

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has been approved by:

• tangenta
• zimulala

To complete the pull request process, please ask the reviewers in the list to review by filling /cc @reviewer in the comment.
After your PR has acquired the required number of LGTMs, you can assign this pull request to the committer in the list by filling /assign @committer in the comment to help you merge this pull request.

The full list of commands accepted by this bot can be found here.

Reviewer can indicate their review by submitting an approval review.
Reviewer can cancel approval by submitting a request changes review.

[tiancaiamao]

/run-unit-test

[zimulala]

LGTM

[zimulala]

/merge

[ti-chi-bot]

This pull request has been accepted and is ready to merge.

Commit hash: b40fd5f

[ti-chi-bot]

@tiancaiamao: Your PR was out of date, I have automatically updated it for you.

At the same time I will also trigger all tests for you:

/run-all-tests

If the CI test fails, you just re-trigger the test that failed and the bot will merge the PR for you after the CI passes.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository.

[sre-bot]

Code Coverage Details: https://codecov.io/github/pingcap/tidb/commit/b40fd5f4d2bfbb5955ec0e4424579761b185c1d7