tests: Fix unstable test alter_pk (#8917)

[ti-chi-bot]

This is an automated cherry-pick of #8917

What problem does this PR solve?

Issue Number: close #8916

Problem Summary:

After executing alter table test.t add primary key new_pk(a,b,c), the table schema is not synced to the latest one when reading from tiflash. Because casting from nullable to not null can be automatically done in the DeltaMergeStore level. So sometime the integration test is not stable. Introduced by #7630

[2024-04-09T07:08:15.819Z] fullstack-test2/ddl/alter_pk.test: Running
[2024-04-09T07:08:24.856Z]   File: fullstack-test2/ddl/alter_pk.test
[2024-04-09T07:08:24.856Z]   Error line: 35
[2024-04-09T07:08:24.856Z]   Error: DBGInvoke query_mapped('desc \$d.\$t', test, t)
[2024-04-09T07:08:24.856Z]   Result:
[2024-04-09T07:08:24.856Z]     ┌─name────────┬─type────────────┬─default_type─┬─default_expression─┐
[2024-04-09T07:08:24.856Z]     │ a           │ Nullable(Int32) │              │                    │
[2024-04-09T07:08:24.856Z]     │ b           │ Nullable(Int32) │              │                    │
[2024-04-09T07:08:24.856Z]     │ c           │ Nullable(Int32) │              │                    │
[2024-04-09T07:08:24.856Z]     │ d           │ Nullable(Int32) │              │                    │
[2024-04-09T07:08:24.856Z]     │ e           │ Nullable(Int32) │              │                    │
[2024-04-09T07:08:24.856Z]     │ f           │ Nullable(Int32) │              │                    │
[2024-04-09T07:08:24.856Z]     │ _tidb_rowid │ Int64           │              │                    │
[2024-04-09T07:08:24.856Z]     └─────────────┴─────────────────┴──────────────┴────────────────────┘
[2024-04-09T07:08:24.856Z]   Expected:
[2024-04-09T07:08:24.856Z]     ┌─name────────┬─type────────────┬─default_type─┬─default_expression─┐
[2024-04-09T07:08:24.856Z]     │ a           │ Int32           │              │                    │
[2024-04-09T07:08:24.856Z]     │ b           │ Int32           │              │                    │
[2024-04-09T07:08:24.856Z]     │ c           │ Int32           │              │                    │
[2024-04-09T07:08:24.856Z]     │ d           │ Nullable(Int32) │              │                    │
[2024-04-09T07:08:24.856Z]     │ e           │ Nullable(Int32) │              │                    │
[2024-04-09T07:08:24.856Z]     │ f           │ Nullable(Int32) │              │                    │
[2024-04-09T07:08:24.856Z]     │ _tidb_rowid │ Int64           │              │                    │
[2024-04-09T07:08:24.856Z]     └─────────────┴─────────────────┴──────────────┴────────────────────┘

What is changed and how it works?

Add DBGInvoke __refresh_table_schema(test, t2); to sync the latest schema of table

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

[JaySon-Huang]

/run-all-tests

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: JaySon-Huang, Lloyd-Pottiger

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [JaySon-Huang,Lloyd-Pottiger]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2024-04-26 07:08:46.428664455 +0000 UTC m=+330483.168567367: ☑️ agreed by JaySon-Huang.
• 2024-05-07 08:51:28.275776096 +0000 UTC m=+952042.032911671: ☑️ agreed by Lloyd-Pottiger.

[ti-chi-bot]

@ti-chi-bot: 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

trigger some heavy tests which will not run always when PR updated.

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.