ddl: allow StatePublic in createTableWithForeignKeys for BR

[YangKeao]

What problem does this PR solve?

Issue Number: close #51838

Problem Summary:

When restoring some tables, the state can be StatePublic, so createTableWithForeignKeys should also handle the StatePublic.

What changed and how does it work?

Also handle the StatePublic in createTableWithForeignKeys. In createTable, the State will always be reset to StateNone (though sounds weird 🤦, but this code has been existing for 8 years).

Check List

Tests

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

  • I checked and no code files have been changed.

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

[codecov]

Codecov Report

Merging #51870 (6408e09) into master (5a2b8e8) will decrease coverage by 14.4470%.
Report is 49 commits behind head on master.
The diff coverage is 100.0000%.

Additional details and impacted files

@@                Coverage Diff                @@
##             master     #51870         +/-   ##
=================================================
- Coverage   70.7104%   56.2635%   -14.4470%     
=================================================
  Files          1477       1592        +115     
  Lines        438429     618687     +180258     
=================================================
+ Hits         310015     348095      +38080     
- Misses       108992     246941     +137949     
- Partials      19422      23651       +4229     

Flag	Coverage Δ
integration	38.6443% <100.0000%> (?)
unit	71.3961% <100.0000%> (+0.8841%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Components	Coverage Δ
dumpling	53.9957% <ø> (ø)
parser	∅ <ø> (∅)
br	57.6044% <ø> (+11.7451%)	⬆️

[YangKeao]

/test pull-br-integration-test

[tiprow]

@YangKeao: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

• /test fast_test_tiprow
• /test tidb_parser_test

Use /test all to run all jobs.

In response to this:

/test pull-br-integration-test

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 kubernetes/test-infra repository.

[YangKeao]

/test pull-br-integration-test

[tiprow]

@YangKeao: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

• /test fast_test_tiprow
• /test tidb_parser_test

Use /test all to run all jobs.

In response to this:

/test pull-br-integration-test

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 kubernetes/test-infra repository.

[YangKeao]

/test pull-br-integration-test

[tiprow]

@YangKeao: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

• /test fast_test_tiprow
• /test tidb_parser_test

Use /test all to run all jobs.

In response to this:

/test pull-br-integration-test

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 kubernetes/test-infra repository.

[YangKeao]

/test pull-br-integration-test

[tiprow]

@YangKeao: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

• /test fast_test_tiprow
• /test tidb_parser_test

Use /test all to run all jobs.

In response to this:

/test pull-br-integration-test

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 kubernetes/test-infra repository.

[YangKeao]

/test pull-br-integration-test

[tiprow]

@YangKeao: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

• /test fast_test_tiprow
• /test tidb_parser_test

Use /test all to run all jobs.

In response to this:

/test pull-br-integration-test

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 kubernetes/test-infra repository.

[YangKeao]

/retest

[YangKeao]

/retest

[YangKeao]

/retest

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2024-03-21 06:38:30.982396392 +0000 UTC m=+1531538.004642782: ☑️ agreed by tangenta.
• 2024-03-21 07:37:06.26019615 +0000 UTC m=+1535053.282442548: ☑️ agreed by zimulala.

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: 3pointer, tangenta, zimulala

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:

• br/OWNERS [3pointer]
• pkg/ddl/OWNERS [tangenta,zimulala]

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]

In response to a cherrypick label: new pull request created to branch release-7.5: #52020.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-6.5: #52021.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-7.1: #52022.