dependency: remove alter-primary config

[GMHDBJD]

What problem does this PR solve?

close #1520

• TiDB nightly use non clustered index default (Even int primary key)
  • now MySQL clustered int primary key will be sync as non clustered in DM ( hope TiDB may change it but not DM🤣
• drop primary key only works for non clustered index

so now drop primary key will not cause an error unless the user creates clustered index manually.

What is changed and how it works?

• fix test
• update dependency
• remove alter-primary config in schemaTracker

Check List

Tests

• Integration test

[GMHDBJD]

/run-all-tests

[ti-srebot]

cherry pick to release-2.0 in PR #1523