[DNM]: test

[joechenrh]

Test-fix PR based on #12654.

Purpose: validate whether the failing DM integration CI is related to the route-aware FK relation path not being wired into syncer.

Change: pass syncer's route resolver into schema tracker FK relation initialization, so the new route-aware builder can validate route alignment instead of always using identity route.

Issue Number: ref #12654

Tests:

• git diff --check
• Local go test was attempted but stopped because first-time dependency compilation did not finish quickly; leaving full validation to CI.

Release note: None

[ti-chi-bot]

Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it.

Details

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-sigs/prow repository.

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign benjamin2037 for approval. For more information see the Code Review Process.
Please ensure that each of them provides their approval before proceeding.

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

Details

Needs approval from an approver in each of these files:

• dm/OWNERS

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]

[FORMAT CHECKER NOTIFICATION]

Notice: To remove the do-not-merge/needs-linked-issue label, please provide the linked issue number on one line in the PR body, for example: Issue Number: close #123 or Issue Number: ref #456.

_{📖 For more info, you can check the "Contribute Code" section in the development guide.}

[joechenrh]

Closing this test PR because it was based on #12654. I will create a separate master-based CI baseline PR instead.

[gemini-code-assist]

Code Review

This pull request introduces route-aware foreign key causality tracking by adding a TableRouteResolver parameter to the downstream foreign key initialization and relation-building processes. This allows the schema tracker to correctly resolve and align routed source tables with their downstream counterparts. Additionally, the caching mechanism was updated to use source table IDs, and comprehensive unit tests were added. The reviewer feedback suggests simplifying a table name string conversion and removing the precheckForeignKeyCausality method, which has become dead code after its call was removed from the syncer.

[gemini-code-assist]

The parentTableName can be simplified by calling sourceParentTable.String() directly, which avoids allocating a new cdcmodel.TableName struct and achieves the exact same string representation.

Suggested change

	parentTableName := (&cdcmodel.TableName{Schema: sourceParentSchema, Table: sourceFK.RefTable.O}).String()
	parentTableName := sourceParentTable.String()

[gemini-code-assist]

Since the call to s.precheckForeignKeyCausality has been removed, the precheckForeignKeyCausality method defined around line 3730 is now unused dead code. Please remove its definition to keep the codebase clean.