[Bug] Ineligible table warning shows empty schema and table_id=0

Description

When creating a changefeed for a table without a primary key or a NOT NULL unique key, the warning prompt may display an ineligible table with an empty schema name and table_id=0.

Steps to Reproduce

1. Create a table without PK/NOT NULL UK (for example test.history).
2. Create a changefeed with default force-replicate = false.
3. Observe the CLI warning/prompt for ineligible tables.

Example output:

[WARN] Some tables are not eligible to replicate, because they do not have a primary key or a not-null unique key: []v2.TableName{v2.TableName{Schema:"", Table:"history", TableID:0, IsPartition:false}}
Could you agree to ignore those tables, and continue to replicate [Y/N]
Note: If you don't want to ignore those tables, please set `force-replicate to` true in the changefeed config file.

Expected Behavior

The warning should show the full table identity, including the schema/database name and a valid table ID (if available), so users can clearly identify which table is ineligible.

Actual Behavior

The warning shows Schema:"" and TableID:0 for the ineligible table entry.

Impact

This is confusing when multiple databases contain tables with the same table name.

Environment

• Repository: pingcap/ticdc
• Observed on branch: master
• Local commit: f08ab832